Method, apparatus and system for use in multimedia signal encoding

ABSTRACT

The present embodiments provide methods, apparatuses, systems for use in encoding and/or formatting content, such as multimedia content. Some embodiments provide methods for use in encoding content. These methods receive source content, encode the source content producing encoded content, evaluate a first encoded segment of the encoded content relative to a plurality of buffer models, determine whether the first segment of encoded content is to be re-encoded relative to one or more of the plurality of buffer models based on the evaluation; and re-encode the first segment when it is determined that the first segment is to be re encoded

PRIORITY CLAIM

This application claims the benefit of U.S. Provisional Application No.60/696,349, filed Jul. 1, 2005, and entitled METHOD, APPARATUS ANDSYSTEM FOR USE IN MULTIMEDIA SIGNAL ENCODING, which is incorporatedherein by reference in its entirety.

FIELD OF THE INVENTION

The present embodiments relates generally to formating of digital data,and more specifically to encoding of digital data.

BACKGROUND

With the increase in the amount of digital content being generated,recorded and/or transmitted, the need to improve the compression andtransmission of the content has also increased. Many compression,encoding and/or standards have been developed and defined to provide forthe compression and transmission of content.

Many of these techniques and/or standards reduce the amount of data thathas to be stored or transmitted. Further, many of these techniques allowfor the reduction of data with minimal reduction in quality of thecontent.

SUMMARY OF THE EMBODIMENTS

The present embodiments provide methods, apparatuses, systems for use inencoding and/or formatting content, such as multimedia content. Someembodiments provide methods for use in encoding content. These methodsreceive source content, encode the source content producing encodedcontent, evaluate a first encoded segment of the encoded contentrelative to a plurality of buffer models, determine whether the firstsegment of encoded content is to be re-encoded relative to one or moreof the plurality of buffer models based on the evaluation; and re-encodethe first segment when it is determined that the first segment is to bere-encoded.

Some embodiments provide methods for use in encoding. These methodsinitiate an encoding of a source content producing encoded content;identify a segment of the encoded content to be re-encoded; identify afirst candidate start point for a re-encoding of the segment; determinewhether the first candidate start point is a valid start point byevaluating a first portion of the encoded content relative to the firstcandidate start point; and set the first candidate start point as avalid re-encode start point when the first candidate start point isvalidated.

Some embodiments further provide method for use in encoding byinitiating an encoding of a source content producing encoded content;identifying a segment of the encoded content to be re-encoded;identifying a first candidate end point for the re-encoding of thesegment; determining whether the first candidate end point is a validend point by evaluating a fourth portion of the encoded content relativeto the first candidate end point; and setting the first candidate endpoint as a valid re-encode end point when the first candidate end pointis validated.

Method for use in encoding content are provided in some embodiments thatreceive source content; encode the source content producing encodedcontent; identify a total bit count for the encoded content; determinewhether the total bit count has a predefined relationship with athreshold bit count; and re-encoding one or more segments of the encodedcontent producing one or more re-encoded segments such that an adjustedtotal bit count with the re-encoded segments has the predefinedrelationship with the threshold bit count when the total bit count doesnot have the predefined relationship with the threshold bit count.

Still further, some embodiments provide method for use in encodingmultimedia content that identify one or more first segments of encodedcontent having a quality level having a predefined relationship with afirst threshold limit; determine whether one or more additional segmentshaving quality levels that have a predefined relationship with a secondthreshold level and are within predefined ranges from one or more of thefirst segments; re-encoding one or more of the additional segmentsproducing one or more re-encoded additional segments having qualitylevels such that the re-encoded additional segments utilize fewer bitsthan the one or more additional segments; and re-encoding one or more ofthe first segments producing one or more re-encoded first segments suchthat the one or more re-encoded first segments have quality levels thatare greater than the quality levels of the corresponding first segment.

Some embodiments provide methods for use in formatting content byparsing an encoded multimedia content stream identifying parameters ofthe content stream; altering one of the identified parameters;simulating at least a partial decoding of the encoded content streambased on the altered parameter; identifying whether a buffer thresholdis exceed; and modifying the encoded content stream according to thealtered parameter when the buffer threshold is not exceeded.

Additionally, some embodiments provide method for use facilitating anencoding of digital content. These embodiments generate a bit rate trackgraphically representing bit rates for portions of encoded content;generate a quality track graphically representing a quality of encodingof the portions of encoded content that corresponds with the bit ratetrack; and identify in the bit rate track a selection of a portion ofthe encoded content to be re encoded.

BRIEF DESCRIPTION OF THE DRAWINGS

The above needs are at least partially met through provisions ofmethods, apparatuses, and/or systems for use in encoding digital contentas described in the following detailed description, particularly whenstudied in conjunction with the drawings, wherein:

FIG. 1 depicts a simplified block diagram of an encoding systemaccording to some embodiments;

FIG. 2 depicts a simplified block diagram of a computer system that canbe utilized in some embodiments to implement the encoding system of FIG.1 and/or to execute some or all encoding and/or re-encoding;

FIG. 3 depicts a simplified flow diagram of a process according to someembodiments for implementing an encoding to achieve an encoded contentthat satisfies one or more desired decoder models;

FIG. 4 depicts a simplified block diagram of a hypothetical referencedecoder (HRD) model according to some embodiments;

FIG. 5 depicts a simplified flow diagram of a process for determiningwhether a segment re-encode is to be performed;

FIG. 6 depicts a simplified flow diagram of a process for evaluatingencoded content;

FIG. 7 depicts a simplified time line representation of a portion of astream of content comprising a plurality of pictures or frames;

FIG. 8 depicts a simplified flow diagram of a process for use inidentifying segment re-encode start points and end points according tosome implementations of the present embodiments;

FIG. 9 depicts a simplified flow diagram of a process for use indetermining and implementing buffer model evaluations relative to are-encode;

FIG. 10 shows a simplified graphical representation of a leaky bucketmodel;

FIG. 11 shows a simplified graphical representation of a leaky bucketmodel according to a variable bit rate;

FIG. 12 shows a graphical user interface according to some embodimentsallowing a user to encode content, review encoded content and/or toimplement and control the re-encoding of one or more segments;

FIG. 13 depicts a simplified graphical representation of the source codecontrol window;

FIG. 14 depicts a simplified graphical representation of the moviecontrol window;

FIG. 15 shows a simplified graphical representation of the timelinewindow according to some embodiments;

FIG. 16 depicts a simplified graphical representation of an enlargedview of the timeline toolbar;

FIG. 17 depicts a simplified graphical representation of an enlargedview of the status bar;

FIG. 18 shows the settings window with the input tab settings windowdisplayed following a base encode;

FIG. 19 depicts the settings window with the video tab settings windowdisplayed following a base encode;

FIG. 20 depicts the settings window with the segments tab settingswindow displayed;

FIG. 21 depicts the settings window with the expressQC tab settingswindow displayed;

FIG. 22 depicts a simplified block diagram of an encoding systemaccording to some embodiments;

FIG. 23 depicts a simplified block diagram representation of a stream ofcontent that is divided into divided segments;

FIG. 24 depicts a simplified block diagram of an example implementationof a dicer according to some embodiments;

FIG. 25 depicts a simplified block diagram of an example a host systemthat can be implemented in the encoding system of FIG. 22;

FIG. 26 depicts a block diagram of a portion of the encoding system ofFIG. 22 according to some embodiments;

FIG. 27 depicts a simplified graphical representation of a complexityprofile or mapping of a content stream scaled to unity that might begenerated through the complexity analyzer of FIG. 26;

FIG. 28 depicts a simplified flow diagram of a process according to someembodiments for the insertion of a chapter point and/or the altering ofgroup of picture (GOP) structures;

FIG. 29 depicts a simplified flow diagram of a process for use inadjusting the total bit count to meet or be below a desired bit budget;and

FIG. 30 depicts a simplified flow diagram of a process for use in smoothor limiting quality changes over a content stream.

Corresponding reference characters indicate corresponding componentsthroughout the several views of the drawings. Skilled artisans willappreciate that elements in the figures are illustrated for simplicityand clarity and have not necessarily been drawn to scale. For example,the dimensions of some of the elements in the figures may be exaggeratedrelative to other elements to help to improve understanding of variousembodiments of the present invention. Also, common but well-understoodelements that are useful or necessary in a commercially feasibleembodiment are often not depicted in order to facilitate a lessobstructed view of these various embodiments of the present invention.

DETAILED DESCRIPTION

The present embodiments provide methods and systems for use in encodingcontent to achieve one or more decoder buffer models and/or encodingschemes. Further, some embodiments allow for the accurate encoding ofcontent such that the encoded content complies with multiple decodermodels according to a desired encoding scheme. Some embodimentsaccelerate encoding and in some implementations additionally provide forthe temporally splitting of the content stream to allow for encoding ofcontent at accelerated rates while maintaining the quality of theencoded content 126. Still further, some embodiments identify portionsor segments of the encoded content to be revised and/or re-encoded, forexample, to comply with one or more non-satisfied decoder models withoutrequiring a full re-encode of the entire content stream.

FIG. 1 depicts a simplified block diagram of an encoding system 120according to some embodiments. The system includes source content 122,an encoder 124, encoder output 126, a content writing system 130, andstorage medium 132. The source content 122, such as video, audio and/orother content is supplied to the encoder 124. The encoder encodes thesource content, in part, compressing the content, for example, to allowthe writing system 130 to reduce the amount of memory space of thestorage medium 132 needed to store the content. The encoding system canbe implemented through hardware, software, firmware and/or a combinationthereof, and can be operated in some instances from a single-processoror multiprocessor computer systems, minicomputers, mainframe computers,processor, microprocessor, as well as personal computers, hand-heldcomputing devices, microprocessor-based or programmable consumerelectronics. Further, in some embodiments, the encoder system 120 can bedistributed over a distributed network with components of the system atdifferent physical locations cooperating to achieve the desired encodedoutput.

As introduced above, the system 120 can be implemented through hardware,software, computer-executable instructions, firmware and/or combinationsthereof, that can be implemented in combination with other programsand/or hardware, software and/or combinations. The encoding and/orre-encoding may also be practiced in distributed computing environmentswhere certain tasks are performed by remote processing devices that arelinked through a communications network. In a distributed computingenvironment, software, executables, scripts and the like can be locatedin both local and remote memory storage devices. A computer and/orcomputer network typically includes computer-readable media, such asvolatile and nonvolatile media, removable and non-removable media, whichcan include RAM, ROM, EEPROM, flash memory or other memory technology,CD-ROM, DVD, HD-DVD, BD or other optical disk storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, and/or substantially any other medium that can be usedto store desired information and from which information can be retrieve.Communication over the computer and/or the network can be through awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless communication connections,and/or other relevant communications or combinations of communicationlinks and/or protocols.

FIG. 2 depicts a simplified block diagram of a computer system 220 thatcan be utilized in some embodiments to implement some or all of theencoding system 120 of FIG. 1 and/or to execute some or all encoding andre-encoding as described above and/or further below. The computer 220can include a processing unit 222, memory 224 and communication link(s)or network 226. The processing unit 222 can be substantially anyprocessor, microprocessor and/or plurality of processors. Thecommunication network 226 directly and/or indirectly couples the systemcomponents together. The memory 224 can include substantially anyrelevant memory such as the memory described above, and can store, data,programs, routines, executables, scripts, audio content, video contentand the like.

The computer 220 can further includes one or more wired or wireless userinterfaces 230 that interface and/or connect devices with the computersuch as keyboard, pointing device, optical and/or audio detectors, touchscreen, stylus, display and/or other such devices. The computer canfurther include ports and/or sockets 232 to couple with external devices240 (e.g., external hard drive, printer, display, and other suchexternal devices) and/or external wired and/or wireless networks 242,244 to communicate with one or more remote servers 246, computers 248,databases 250 and/or other such devices.

Referring back to FIG. 1, the encoder 124 is typically configured toencode the content 126 according to a given standard or scheme that iswell recognized, such as MPEG2 (Moving Picture Experts Group). Otherencoding schemes are alternatively and/or additionally utilized, andsome of these are typically employed for relatively higher bit ratecontent, such as high definition video content, high resolution content,and include MPEG4 part 10 AVC, VC-1 (WMV9), and other such encodingschemes. The encoding according to at least some of these standards ismore complex than MPEG2, in part, because some of these standards, suchas AVC and VC1, provide for a plurality of decoder requirements, such aspluralities of decoder buffer models to be satisfied for each encodedcontent 126.

The present embodiments, allow for the accurate encoding of content tosatisfy a plurality of decoder models according to a desired encodingscheme. Further, some embodiments provide for accelerated encoding, insome implementations, by splitting the content stream across multipleencoders and/or processors while maintaining the quality of the encodedcontent 126. Still further, the present embodiments allow for userselected and/or automated selection of portions or segments of theencoded content to be revised and/or re-encoded, for example, to complywith one or more non-satisfied decoder models.

FIG. 3 depicts a simplified flow diagram of a process 320 according tosome embodiments for implementing an encoding to produce an encodedcontent that complies with one or more desired decoder buffer models. Instep 322, the source content is received. The content can be receivedfrom an recorded medium (e.g., tape, disc, or other such medium), thecontent can be initial content received from a recording device, thecontent can be acquired from a local data storage or from a remote datastorage (e.g., accessed over a distributed network such as theInternet), and other such sources or combinations of sources. In step324, the content is encoded according to the one or more decoder buffermodels. In step 326, the encoded content is evaluated. The evaluationcan be performed as the content continues to be encoded, or following acomplete encode of the content. In step 330, the process determineswhether one or more segments of encoded content fail to meet one or moreof the desired decoder buffer models. In some implementations, one ormore quality threshold levels, such as peak signal-to-reconstructedimage comparisons as described below, are evaluated relative to theoriginal content.

When one or more segments are identified in step 330 as failing tosatisfy one or more models and/or fails to satisfy quality limits, theprocess enters step 332 where it is determined whether one or more ofthe identified segments are to be re-encoded. When a segment is to bere-encoded, step 334 is entered and the one or more identified segmentsare re-encoded. In step 336, the re-encoded segment is evaluated todetermine whether the re-encoded segment satisfies one or more of thepreviously unsatisfied decoder buffer model. When the re-encoded segmentfails to meet the models, the process returns to step 332 to determinewhether the segment is to be again re-encoded. When the encoded segmentdoes satisfy the model(s), the process enters step 340 and determineswhether further segments are to be evaluated and/or re-encoded. Whenadditional segments are to be re-encoded the process returns to step 332to determine whether the one or more segments are to be re-encoded, andalternatively, when there are no further segments to evaluate theprocess continues to step 344.

In step 344, the process determines whether additional processing of theencoded content is to be performed, such as the inclusion of one or morechapter points (e.g., through a segment re-encode with the inclusion ofan entry point) or other processing as described below. When furtherprocessing is to be performed, step 346 is entered where furtherprocessing is performed. Alternatively, step 350 is entered where theencoded content is finalized and/or stored. Upon finalizing and writingthe content, those portions of the content that were re-encoded arewritten instead of the initially encoded content that failed to meetbuffer model parameters and/or quality limits.

Limiting the re-encoding of content to segments of the content insteadof having to re-encode an entire stream at least significantly reducesencoding time, increases processing speed, reduces processing overhead,improves overall encoding performance and verifies that the encodedcontent satisfies desired decoder buffer models, effectively satisfyingone or more encoding standards, such as AVC, VC1, and/or other encodingschemes and provides other benefits as described above and furtherbelow.

Segment based re-encoding provided by some embodiments allows for theefficient replacement of portions or regions of encoded (e.g.,compressed) content, such as video data, within a pre-existing encodedcontent stream with a segment that has been re-encoded according to oneor more altered encoding parameters (e.g., encoded according toincreased bit rates, transrating, and other encoding parameters ortechniques) such that the resulting cooperated encoded content satisfiesone or more standards and/or decoder models. Many previous systemstypically required a re-encode of the entire video stream when one ormore sections had errors and/or failed to meet decoder models. There-encoding of the entire stream adds significant amounts of processingtime to the encoding process and can dramatically reduce productivity.Some existing systems allow for a type of re-encoding according to thesingle, well defined and established standard of MPEG2. The re-encodingto satisfy MPEG2, however, cannot be applied to many other encodingstandards, such as AVC, VC1 and many other encoding standards. This isdue in part to the fact that MPEG2 only provides for satisfying a singlebuffer model, while other encoding schemes such as AVC and VC1 aredefined such that encoded content in many instances satisfy multiplebuffer models.

Some embodiments allow one or more individual segments of encodedcontent to be modified and re-encoded, and then the re-encoded segmentsare incorporated back into the main encoded stream. Thus, someembodiments avoid the need to go back and do a complete re-encode of theentire content stream (e.g., a two hour movie). Instead, the presentembodiments allow a segment, such as a one minute segment, 30 secondsegment, 10 second segment, 1 second segment, less than a second and/orsubstantially any length segment to be re-encoded and incorporated backinto the encoded stream drastically reducing the time needed to achievean encoding of a content stream that satisfies desired parameters.

As introduced above, some embodiments allow content to be encoded tosatisfy more than one decoder buffer model. These buffer models definehow data is taken in and released out of the decoder. The presentembodiments provide for segment re-encoding while still conforming tothese generally strict standards (as typically spelled out in encodingspecifications such as the specifications for AVC or VC1) where theresulting encoded stream satisfies a plurality of decoder buffer models.These decoder buffer models are typically different for AVC and VC1 thanfor MPEG2, because in part the MPEG2 encoding typically only has tosatisfy an single buffer model, while encoded streams meeting AVC and/orVC1 standards can satisfy a plurality of models.

Satisfying the plurality of models provides for more flexibility on thedecoder side because a decoder simply has to satisfy any one of themultiple models (leaky bucket models) allowing the decoder to decode thestream. Alternatively, in MPEG2, there is a single model to besatisfied. Further, the benefit of satisfying multiple models allowsdifferent decoders to decode the stream, e.g., some decoders may have arelatively fast fill rate but a relatively small buffer, while otherdecoders may have a relatively large buffer with a relatively slowerfill rate. Typically, a decoder can access the encoded stream andidentify up front whether the decoder can decode and playback thestream.

The system can further analyze encoded content to determine and/orverify whether one or more decoder buffer models and/or parameters aresatisfied. The verification of satisfying models is performed, in someimplementations, by simulating the behavior of decoders and the waythose decoders decode a stream in terms of consuming data from anassociated buffer. In some implementations, the system sequentiallysimulates one model at a time. Some implementations evaluate multiple orall of the potential models substantially simultaneously, by simulatingthe models in parallel. The system extracts the data from thesimulations, whether performed sequentially or in paralleled, and thendetermines whether one or more decoder models fail.

To perform the simulation of the one or more decoders, some presentembodiments employ one or more hypothetical reference decoders (HRD)that are, in some implementations, a mathematical model of one or moredecoders and their input buffers. This HRD is defined according todesired standards to be met by the encoded stream, such as by one orboth AVC and VC1 standards. Typically, for a given encoded stream to becompliant with the desired standard, the stream conforms to thereference models given the parameters of the models specified in thestream. The relationship between the decoder and its input buffer in theHRD is defined in terms of a “leaky bucket” buffer model. This buffermodel specifies the parameters for how the buffer fills and is emptiedin terms of bit rate (bits per second) and buffer fullness. For a streamto be compliant with, for example, AVC and VC1 it should specify one ormore sets of decoder model parameters for which the HRD runs withoutexceeding the buffer fullness range.

The HRD in some preferred implementations can define multiple models atonce for which the encoded stream is to conform. For example, the HRDcan define 5, 10, 20, 100 or more buffer models with different fillrates and with different sizes, and the encoded signal is to conform toa plurality of these different buffers, and in some instances all of thedifferent models.

The HRD performs a simultaneous verification of a plurality, andpreferably all designated possible buffer models at once to see if oneor more models fail. When one or more models are identified as failed,the system and/or user can go back and fix the stream, by performing asubsequent re-encode of one or more segments of the encoded stream.Alternatively, the system and/or user may determine or decide not tosatisfy and/or cannot satisfy one or more models, due to the nature ofthe content at that particular point (at any one or moreportions/sections), then the present system can change the parameterdesignations in the stream to identify that the encoded stream isactually supporting less than all of the buffer models according to astandard (e.g., AVC and/or VC1). For example, some embodiments maintainas meta data those decoder buffer models that are not satisfied by theencoded stream. Upon storing the encoded content, the models that arenot satisfied by the final encoded content are not identified in aheader or parameter data, or can be identified as unsatisfied indesignation, header, and/or parameter data of the storage medium (e.g.,a disc, compact disc (CD), digital versatile disc (DVD), other opticallyreadable medium, and/or other mediums).

Typically MPEG2 systems during an encode specify “in” and “out” bufferlevels for which the encoder is instructed to try and achieve. Often thebuffer does not achieve the out-point correctly, and therefore downstream the buffer model fails. Some MPEG2 systems attempt toautomatically implement another encode of the entire content stream atan altered bit rate in an effort to fix the one or more regions thatfailed the model so that eventually the entire stream is compliant. Thishas an effect of reducing the overall encoding quality of the entirestream.

Alternatively as introduced above, some embodiments attempting to complywith multiple models can identify when one or more segments of thecontent fails one or more of the plurality of models, and rather thansubsequently initiating a re-encode instead just invalidates the buffermodel that failed. Thus, some embodiments can avoid attempting are-encode so that the encoded stream satisfies less than all modelsdesignated in a stream.

FIG. 4 depicts a simplified block diagram of an HRD model 420 accordingto some embodiments. The HRD 420 includes a processor 422 with one ormore of decoder models 424-426. In some embodiments, the processor 422is implemented, at least in part through a process of an encoder, suchas encoder 124. The processor 422 includes and/or accesses a decodermodel for each model to be evaluated according to the standard (e.g.,AVC, VC1, and the like). The processor 422 can be implemented through acomputer or computer system (e.g., computer system 220), microprocessor,logic and other processing circuitry as is known in the art capable ofimplementing the desired decoder evaluation. In some embodiments, thedecoder models 424-426 are implemented through software, for example asobject oriented programs and/or vector of classes configured to mimicthe processing requirements of a decoder according to defined buffermodels (e.g., the fill rate, buffer size, and other parameters). In someembodiments, the HRD optionally incorporates a plurality of processorsor computers 422, 440, 442, each with one or more decoder models424-426, 450 and 452 such that the processing capacity for the HRD isdistributed over the plurality of processors 422, 440, 442. Theprocessors can be co-located and/or be distributed over a network, suchas an intranet, the Internet, or other such networks.

The encoded content 430 is supplied to the HRD 420. Each element of thedata set is fed to each decoder model 424-426 (and optionally 450, 452).The models each process that particular data serially or in parallel andlook for errors occurring in the decoded stream. Upon evaluation of anelement, the subsequent element is fed to the models and is evaluated.The system continues to loop back such that each element of the streamis directed to each decoder model 424-426 for evaluation, and the streamis fully evaluated. In some embodiments, the HRD 420 is employed toevaluate the encoded stream as the content stream 122 is being encoded.The HRD can, in some implementations, further provide predictivefeatures of the content stream for use in encoding and configuring theencoded content. For example, the HRD can include a simplified encoder,such as an MPEG2 encoder, that processes the video content. Based on theencoding achieved through the HRD MPEG2 encoder the HRD is able toidentify or predict estimated buffer levels, encoding rates for AVC,VC1, MPEG4 and/or other encoders, and other encoding parameters.

FIG. 5 depicts a simplified flow diagram of a process 520 forimplementing segment re-encodes. In step 522, errors identified throughprocessing of the encoded content, such as through the HRD, areretrieved. In step 524, the errors are evaluated and the processdetermines whether one or more segment re-encodes are to be performed.The determination of whether a re-encode is to be initiated can be basedon one or more factors. In some implementations, the determination of are-encode is specified by a user. The system can identify areas wherebuffer models fail, and implement re-encode and/or allow a user todesignate areas to be re-encoded. In some embodiments, the re-encodescan be initiated for substantially any segment failing to meet buffermodels. Further, some embodiments limit the segment re-encodes to areaswhere the buffer model is not met and the subsequent re-encode does notdegrade the quality of the segment below a threshold. Additionallyand/or alternatively, the segment re-encode can be implemented when aquality falls below a threshold and sufficient bit resources areavailable to re-encode at higher bit rates. Other factors and/orconditions can be utilized to determine when re-encodes are to beinitiated as are described below.

When the re-encode is to be performed, step 526 is entered where are-encode is initiated for an identified segment. In step 530, theprocess determines whether one or more errors are detected for there-encoded segment for one or more decoder models. If further errors aredetected for the re-encoded segment, the process again determines instep 532 whether a subsequent re-encode of the segment is to beimplemented. Again, many factors can and/or are reviewed to determinewhether a re-encode is to be initiated, such as but not limited to,determining whether the re-encode significantly degrades the quality ofthe content (e.g., beyond a threshold), available bits, threshold levelsand/or other factors. If a subsequent re-encode of the re-encodedsegment is to be performed, the process returns to 526. Alternatively,when a subsequent re-encode is not to be performed the process skips tostep 536.

When the re-encoded segment meets desired buffer models as determined instep 530, the process enters step 534 where the re-encoded segment isstored, in some embodiments the re-encoded segment is stored in aseparate file or storage location. The process then continues to step540. If it is determined in steps 524 and 532 that re-encoding is not tobe performed for segments where errors are detected, buffer models thatfail for the identified one or more segments are recorded as failing instep 536. In some instances the failed buffer models are stored in aseparate file. In step 540, the process determines whether furthererrors are to be evaluated for re-encode. When additional errors are tobe evaluated, the process returns to step 522, otherwise the processcontinues to step 542.

In step 542, the recording of the encoded stream is initiated where thedecoder buffer models identified in step 536 as failed for one or moredecoder models are removed from a header of the stream and the buffermodels that the encoded stream satisfy are recorded. In step 546, therecording of the encoded content is begun. In step 550, those segmentsthat have been re-encoded are identified during the recording of thecontent. In step 552, the process replaces the initially failed encodedsegments or other segments that were re-encoded with and/or stitches inthe re-encoded segments (e.g., retrieves the re-encoded content from aseparate file and replaces the failed segment with the retrievedre-encoded segment), and write the re-encoded segments. In step 554, theprocess determines whether further encoded content is to be written andreturns to step 546 to continue writing the encoded content and there-encoded content. Alternatively, the process terminates.

In some implementations, for those segments that fail to satisfy decoderbuffer models and a re-encode of that segment does not achieve a desiredquality and/or still fails to satisfy the desired decoder buffer model,the content stream proximate the failing segment is further evaluatedand/or re-encodes of neighboring segments are further implemented. Byre-encoding surrounding segments of the segment of interest, the buffermodel requirements for the segment of interest can be reduced such thatthe re-encoded segment satisfies in and/or out rates of the buffermodel. Further, the re-encoding of neighboring segments can be utilizedto simplify or more readily allow the incorporation of the re-encodedsegment back into the encoded stream following the re-encode.

Some embodiments improve the encoding process and processing time byallowing for the re-encoding of just segments of content instead ofrequiring a complete re-encoding of an entire stream, and incorporatingthe re-encoded segments into the final encoded content so that thestream satisfies the desired encoding standard and/or the desireddecoder models. Further, some embodiments can prevent unnecessaryre-encodes that would be needed to satisfy one or more invalidatedbuffer models for models that are not desired and/or cannot be satisfiedwithout significantly degrading the overall quality of the content. Forthose models that are not desired and/or cannot be satisfied withoutdegrading the quality beyond a threshold (which can be user defined,system defined, buffer model defined), some embodiments provide for theidentification of those buffer models that are not satisfied andinvalidate those models for the content stream. By simply identifyingand/or invalidating the decoder model parameter sets that are notsatisfied following a re-encode, for example due to not achieving atarget segment out point buffer level for a given re-encode, the systemimproves overall content quality, reduces processing overhead, andreduces processing times.

As introduced above with respect to FIG. 5, some embodiments improveprocessing time and reduce processor overhead by cooperating orstitching the re-encoded segments back into the encoded stream ofcontent when the processing of the encoded stream is complete and theencoded content is to be written as a final form (e.g., writing to a DVDor other medium). In these embodiments, the initial base encode isperformed followed by the identifying of the segments that are to bere-encoded, performing the re-encodes and maintaining the re-encodedsegments in one or more separate files, and generating links to identifywhere in the encoded stream the re-encoded segments are to beincorporated. When the re-encodes and other processing is completeand/or when a user is satisfied with the encoded end result, theencoding process is finalize where those models that are invalidated areidentified, the one or more re-encoded segments are stitched back intothe encoded stream replacing those segments identified to be re-encoded,and the invalidated models and the entire revised encoded stream arestored. The invalidation of one or more models may vary from codingscheme to code scheme. For example with AVC, the invalidation of modelscan be achieved in some implementations by reconstructing an hrdparameter data structure in the stream with new data that does notcontain the invalidated model parameters. Some embodiments further allowthe user and/or the system to implement additional segment re-encodes,full re-encodes and/or other processing after finalizing the encodedcontent, and then re-finalizing again for storing of the altered encodedstream.

In evaluating a stream of content that has been encoded, someembodiments can determine whether the encoded stream satisfies desireddecoder models and/or determine a quality or degradation of the signaldue to encoding. Some embodiments implement a comparison of the decodedstream (e.g., decoded through the HRD) with an original content stream,an evaluation of the picture quality, an evaluation of the quality ofpicture parameters, and/or other evaluations or combinations ofevaluations. For example, in some implementations, the evaluation of thepicture quality following an encoding is achieved by employing JustNoticeable Difference (JND) methodology or algorithm that quantifies thepicture quality impairments associated with compressed videoapplications. JND is sensitive to a variety of picture defects and worksover a range of picture qualities resulting in predictions that attemptto closely match human visual evaluations. Additionally and/oralternatively, algorithms that approximate the results of the JNDmethodology (e.g., Sarnoff) can be employed.

Signal to noise ratios (SNR) and/or peak signal-to-reconstructed image(PSNR) comparisons can additionally and/or alternatively be employed todetermine the encoded quality. PSNR is essentially a measure of quality,distortion and/or a determination of how closely the encoded contentafter being decoded matches the original content. Other encoding and/orimage evaluations can be utilized as are known in the art to determinethe quality of the encoded content, such as identifying areas of frameswhere motion vectors are diverse or varying; evaluating compressionscheme formation vectors; evaluating values of quantization, macroblockeffects, areas with redundancy, and other factors to identifying blocksthat potentially are more likely to exhibit error for measuring thequality of encoding; and other methods for assessing quality orcombinations of methods can be utilized.

In determining the quality of the content the system in someimplementations obtains the quality data (e.g., JND and/or PSNR data) asa part of the encode process by performing a partial decode of thecontent during the encoding. Typically, the partial decode can beinitiated prior to a complete encoding of the content, but at a stagewhere at least some of the negative effects of encoding the content canbe evaluated. The partial decode produces content that can be evaluatedand/or produces substantially fully decoded frames that are thenevaluated (e.g., PSNR value(s), JND value(s), and/or some other measureof distortion). Typically, encoding is a layered set of encodingprocesses, utilizing for example, discrete cosine transform (DCT), interframe compression going from one frame to another, entropy encoding,quantization, and/or other encoding layers. The partial decode can beinitiated for example through the HRD 420 to evaluate the stream at atime between one or more layers of encoding to generate the desiredPSNR, JND or other evaluation results. The evaluation results are thencompared with threshold levels to obtain a measure of encoding qualitythat can be returned to the encoding processor.

The selection and use of PSNR, JND and/or other parameters forevaluating the quality of the encoded signal can depend on many factors,including processing capabilities and/or overhead, expected run times,the speed at which results are needed and other factors. For example,when evaluating encoded content at real time rates, the system may limitthe evaluation to PSNR as determining PSNR typically employs analgorithm that is relatively quick. In instances where speed ofevaluation is not as critical and/or signal processing capabilities aresufficient, JND evaluations may be used.

Some implementations utilize a plurality of comparisons and/or qualityevaluations, such as using both PSNR and JND. The system can, in someimplementations, further allow a user to select which one or morecomparisons are employed to evaluate the encoding and to determinequality. Similarly the user can specify a weighting between multiplealgorithms and/or comparisons (depending on the advanced level of theuser), and further, the amount of processing power to be utilized.

The evaluation can be performed on an entire frame, with evaluationsimplemented on a frame by frame basis, sub-frame by sub-frame basis, orgroupings of frames. To compensate for processing speed and/orprocessing overhead, in some implementations, the system employs astatistical sampling mechanism to randomly, arbitrarily, and/orselectively take one or more blocks of content within a particular imageand sample the current PSNR value, the JND value and/or other evaluationtechniques, for the one or more blocks. The sampling allows for astatistical mapping to be generated of overall distortion of the imagebeing sampled. In some implementations, the sampling provides sufficientinformation to accurately evaluate the encoded signal and to provideadjustments to the encoding levels. In selecting the blocks to sampleand/or to guide the evaluation, some embodiments check for regions wheremotion vectors vary or are moving relatively widely, compression schemeformation vectors, values of quantization (where coarse values ofquantization can imply relatively large amounts of compression), andother factors to identify blocks that potentially are more likely toprovide a relatively accurate representation of encoding quality and/orexhibit one or more error(s) for measuring the quality of encoding.

FIG. 6 depicts a simplified flow diagram of a process 620 for evaluatingencoded content. In step 622, at least a portion of the content streamis decoded as the stream is being encoded. In step 624, one or moreareas within a frame or picture are identified such as areas ofrelatively high compression. In step 626, at least those areasidentified are evaluated, and the results of the evaluation are comparedwith one or more threshold levels. In step 632, the process determineswhether the results meet or exceed (or fall below depending on theparameter being evaluated and/or the threshold limit) the one or morethreshold levels. When the results of the evaluations meet thethresholds, and thus quality levels are satisfactory, the process skipsto step 642.

Alternatively, when the quality falls below threshold limits, theprocess enters step 634, where it is determined whether a re-encode isto be performed. Again, this determination can be made by the processand/or system based on the threshold levels. Alternatively, the systemcan identify those areas of the encoded stream with potential qualityproblems and allow a user to select those segments to be re-encoded. Forexample, a report and/or time line can be generated that identifiesthose areas with potential quality problems, with relatively highcompression, where decoder models fail and/or potential errors occur,and/or other relevant information. When a re-encode is to be initiated,the process enters step 636 where a segment re-encode is initiated.Following the re-encode, the process returns to step 624.

When a re-encode is not to be performed, step 640 is entered where theone or more decoder models that have failed for the identified segmentsare recorded. In step 642, the process 620 determines whether the end ofthe encoded content stream has been reached. If not, the process returnsto step 622. Otherwise the process terminates.

As is known in the art, some encoding schemes and/or standards, such asAVC, VC1, MPEG2 and other encoding schemes reduce the amount of datathat has to be maintained by defining one picture or frame byreferencing one or more different frames. For example, a first frame canreference a second frame and define changes that are to be made to thesecond frame to achieve the first frame. As a further example, the AVCcompression scheme typically relies on inter frame prediction of framesfor significant coding efficiency gains. The type of inter predictiondepends on the frame type, whether a P-frame (predictive frame), aB-frame (bi-directionally predictive frame), an I-frame (intraframe), orother defined frame type. P-frames typically can be predicted from oneother reference frame, and B-frames typically can be predicted from acombination of two other reference frames. Some embodiments inimplementing a segment re-encode attempt to avoid disrupting interprediction schemes between multiple frames, and/or re-designate thereferencing to provide accurate decoding.

For example, some encoding specifications, such as AVC, specify how themanagement of referenced frames is to be maintained and implemented bydefining reference frame lists (for AVC two reference frame lists aretypically maintained, some times referred to as L0 and L1) that are usedto store indexes of reference frames. A decoder during decodingmaintains storage of reference frames indexed by either L0 or L1. Whendecoding a frame, the lists L0 and/or L1 are accessed to identify otherframes that are references for the decoding of the frame of interest tolocate appropriate reference frames for use in reconstructing the frameof interest.

Further, in some encoding schemes, such as MPEG2, frames of pictures aregrouped together (called a group of pictures, or GOP), such as when thecontent is visual content. Because of the organization and/or structureof a GOP, which typically start with an I-frame, include P-frames atregular intervals through the GOP and one or more B-frames between eachpair of I/P frames, and does not allow inter prediction between closedGOPs, the encoding scheme provides convenient intervals for employingsegment re-encodes. With MPEG2 it is typical to have GOPs that arerelatively short or contain a relatively small number of frames. Forexample with MPEG2, a GOP typically includes about 13-15 pictures orframes equating roughly to about a half second interval of time duringplayback (when playing back at 30 frames per second, i.e., 15/30 persecond or about ½ second). The relatively short GOPs simplify theidentification of re-encoding start and end points with MPEG2.

Other encoding schemes, however, such as AVC, VC1 and other relevantencoding schemes often do not define GOP structures or have GOPstructures that are typically much larger and/or longer relative toMPEG2 GOP structures. For example, GOP structures for AVC can in someinstances include 150 or more frames or pictures (which typicallyinclude multiple I, B, P and/or IDR frames). As a result, whenre-encoding according GOPs encoded with a scheme such as AVC or VC1, there-encoding can result in large numbers of pictures being re-encoded,which can be computationally expensive and time consuming. Further, along GOP is often an inconvenient or difficult level of granularity forre-encoding.

Some embodiments provide for the ability to initiate a segment re-encodewithin a GOP and/or at sub-GOP levels to reduce the length of a segmentthat is to be re-encoded, reduce the processing overhead, as well asreducing processing time. The initiating of a re-encode within a GOP orat sub-GOP levels of granularity is achieved by identifying start andend pictures or frames within a stream that bound a series of frames tobe re-encoded where frames outside these start and end picture bounds donot reference frames within these bounds, and/or by upgrading a P- orB-frame to an I-frame to starting the re-encode at that upgraded P-frameor B-frame.

FIG. 7 depicts a simplified time line representation of a portion of astream of content 720 comprising a plurality of pictures or frames 722.The time line is an index representation of coded pictures. For ease ofaccess and user understanding, the time line in some implementations canbe generated relative to time display order 726 as apposed to an encodeorder. As indicated above, the frames are typically defined according toa frame type and in the example of FIG. 7 are designated as I-frames,B-frames, P-frames and IDR-frames. Prior to initiating a segmentre-encode, some embodiments evaluate segments of the stream 720 relativeto portions to be re-encoded to determine if and where re-encoding canbe implemented in attempts to avoid disrupting the picture referencingand/or dependency.

Some embodiments evaluate the frames 722 of the stream 720 to identifyone or more segment re-encode start or in-points, and one or more end orout-points. In some instances, for example when satisfying AVC, thereference lists L0 and L1 are utilized to determine other frames that aframe of interest references (e.g., frame of interest B-picture 730references an I-picture 732 four frames into the future and a B-picture734 five frames in the past). The reference lists L0 and/or L1 areaccessed to determine one or more reference pictures into the futureand/or one or more reference pictures into the past.

As described above, some encoding standards provide for the referencingof multiple frames and reference lists are used to store an index ofreference pictures. A decoder maintains storage of reference picturesand uses the lists to look up the reference frames to implementprediction. During the segment re-encode, some systems attempt to avoiddisrupting the referencing to other frames or pictures. In evaluatingthe stream 720 some embodiments attempt to identify appropriatere-encode start points and/or end points by determining whether picturesoutside a proposed segment are referencing pictures within the proposedsegment to be re-encoded. In some implementations, an index is generatedcontaining information, such as a data structure, that containsinformation relevant to the pictures of the stream, such as a picturetype (e.g., I, B, P, IDR), duration, size in bits, in some instances abuffer state (e.g., such as the HRD buffer state), and/or other relevantinformation. The index for a picture can also contain an index orlisting 752, such as a timeline index, of the other pictures 754-758 inthe encoded stream that reference that picture.

This list 752 of other pictures can be stored in many different formatsand/or configurations, and in some implementations is stored asmetadata, and/or a list attached with time line picture data structures.For example, FIG. 7 shows an I-picture 750 with a reference list 752that identifies each picture 754-758 that is referencing that I-picture750. This index allows the system and/or user to quickly and easilyidentify other pictures referencing a picture being considered.

The index 752 of pictures referencing a picture can includesubstantially any number of pictures. For example, a frame of contentthat generates a display screen that is entirely black that ispositioned at the beginning of a stream or GOP can be referenced by allother black frames in the stream or GOP. In some implementations,however, particular profiles and levels of encoded stream can set uplimits on the number of pictures that can reference a picture.

The list 752 simplifies the evaluation of the stream 720 to identifypotential start points and end points of a segment or sub-GOP that is tobe re-encoded. A search algorithm can be employed that identifies thepictures that reference a picture of interest by accessing the referencelist 752. Additionally and/or alternatively, the systems can employ analgorithm that is used to determine the pictures that a picture ofinterest references.

The re-encode segment identification algorithm identifies segment startand end points along the stream of content 720. Some embodiments attemptto identify start and end points at or near the portion of the streamthat is identified to be re-encoded. Further, some embodiments set alimit defining a reasonable position or number of pictures away from thesegment identified to be re-encoded. For example, when a user selects tostart a re-encode at about a time “T” (e.g., about 50 seconds into thestream), the user is going to expect the start point of the segmentre-encoded to be around that “T” point. Therefore, the limit attempts toensure the determined start point is proximate the requested startpoint. Some embodiments identify a plurality of potential start and endpoints. Based on the plurality of potential start and end points, theuser can select which points to use.

FIG. 8 depicts a simplified flow diagram of a process 820 for use inidentifying segment re-encode start points and end points according tosome embodiments. Referring to FIGS. 7 and 8, in step 822, a candidatestart point picture is identified relative to a segment that isidentified during the evaluation of the stream of content 720. Forexample, step 822 can include determining whether there is an I- orIDR-picture within a predefined limit of the segment identified to bere-encoded (such as a segment identified in step 534), selected by auser, an identification through a comparison with the original content,and/or other methods of identifying a candidate picture. In step 824 theprocess 820 scans to a subsequent picture relative to the selectedcandidate start picture, for example, forward on the time line 720 onepicture.

In step 826, the reference list 752 for the picture being evaluated isaccessed when available to determine whether a picture previous to theidentified candidate start point picture references the picture beingevaluated and thus is outside the potential segment or other evaluationsare performed to determine reference pictures. If it is determined thatone of the scanned pictures is referenced by a picture previous (e.g.,to the left in FIG. 7) to the candidate start point, the process entersstep 832 where the candidate start point is defined as an invalid startpoint. In step 834, a new candidate start point is selected (e.g., apicture previous to (in FIG. 7, to the left) of the previous candidate)and evaluated. Typically, the subsequent candidate start point pictureis at least the picture identified in step 826 or previous to thatpicture. This evaluation attempts to ensure that the segment is selfcontained, and pictures outside the segment are not referencing pictureswithin the segment because of the potential changes that are likely toresult to the pictures within the segment following the re-encode. Theprocess then returns to step 826 to evaluate the subsequently selectedcandidate start point.

When it is determined in step 826 that the picture being evaluated isnot referenced by a picture beyond the candidate start point, step 830is entered where the number of forward pictures evaluated is comparedwith a predefined threshold, such as to the size of a decode picturebuffer. Typically, the evaluation forward does not need to go beyond thesize of a decode picture buffer because a decoding system typicallywould not reference a picture beyond this point because the referencedpicture is to be decoded before the current picture is decoded.

When it is determined in step 830 that the number of pictures evaluatedfrom the candidate start point does not equal or exceed the threshold(e.g., buffer size), the process returns to step 824 to evaluate anotherpicture within the segment to be re-encoded. Alternatively, when thenumber of pictures evaluated equals or exceeds the limit and thepictures are not referenced by pictures previous to the candidate startpoint, step 836 is entered where the candidate start point is defined asa valid start point.

Once a candidate start point is identified as valid in step 836, an endpoint picture of the segment to be re-encoded is identified. In step840, an initial end point candidate is selected and the system scansbackward through the pictures of the candidate segment from thecandidate end point until the identified start point picture, anIDR-picture (e.g., with AVC) or other indicator is reached to furtherdetermine whether pictures outside the proposed re-encode segmentreference pictures within the segment. As indicated above whenevaluating the start point, the pictures evaluated from the start pointforward is typically limited to the size of the decode picture buffer.When evaluating the pictures back from the candidate end point theretypically is not a limit to the number of pictures that are evaluated,and in some instances the pictures all the way back to the start pointpicture are evaluated. Reference pictures, however, typically do notreference pictures beyond an IDR-picture in a backwards direction formany encoding schemes such as VC1 and AVC. An IDR-picture is intrapredicted and thus does not reference other pictures. In addition, thearrival of an IDR-picture typically causes a decoder to flush currentlystored reference pictures, and thus, subsequent decoded pictures indecode order typically do not reference a picture prior to theIDR-picture.

In step 840, a candidate segment re-encode end point is selected. Again,the end point is selected near a segment identified to be re-encoding,and can be selected by a user, can be an I- or IDR-picture proximate thesegment to be re-encoded and other selection methods. In step 842, theprocess 820 determines whether the picture being evaluated is referencedby a picture beyond the identified candidate end point picture (e.g., tothe right of the candidate in FIG. 7). In some embodiments, theevaluation in step 842 is simplified by using reference list(s) 752. Ifthe picture being evaluated is referenced by a picture beyond thecandidate end point a new candidate end point is selected in step 850and the process returns to step 842 to evaluate pictures relative to thenew candidate end point.

When it is determined in step 842 that the picture being evaluated isnot referenced by a picture beyond the candidate end point, step 844 isentered where it is determined whether the picture being evaluated isthe segment re-encode start point picture identified in step 836. If thepicture being evaluated is the start point picture, the processcontinues to step 854, otherwise the process moves to step 846. In step846, the process determines whether the picture being evaluated is anIDR-picture. If the picture is not an IDR-picture, the process continuesto step 852 to select the preceding picture and then returns to step 842to revaluate the selected preceding picture.

In steps 844 and 846, when it is determined that the picture beingevaluated is the start picture or an IDR-picture, the process identifiesthe candidate end picture as a valid segment re-encode end picture instep 854 defining the bounds of the segment to be re-encoded. Typically,pictures do no reference pictures beyond an IDR-picture in a backwardsdirection due to flushing of caches and the like, and thus, theevaluation can be halted at an IDR picture and the candidate end pointpicture is identified as valid thus establishing the bounds of a segmentto be re-encoded.

In some implementations, the selection of candidate start point picturesin step 822 is limited to I-frames, at least in part to limit thereferencing that the candidate start point picture has to implement,where pictures prior to the I-frame do not reference that I-frame orpictures beyond the I-frame. Alternatively, some embodiments allow thecandidate start point pictures to be B- and/or P-pictures. For example,a B-picture typically references one or more frames that have alreadybeen decoded before the B-picture can actually be decoded. As such, someembodiments in implementing the re-encode starts a re-encode and resetsor redefines the referencing of the B-picture so that the B-picture isreplaced with an I-picture that does not reference previous frames.Therefore, some embodiments compensate for long GOPs (e.g., GOPs in AVCand VC1 encoding schemes) by defining sub-GOPs and re-encoding thesub-GOP.

Prior to generating an I-picture and/or converting a B- or P-picture toan I-picture, some embodiments verify that the buffer and/or processingoverhead associated with the upgrading to the I-frame is available. Forexample, the selection of the P-frame to be upgraded is selected and isverified that there is sufficient processing buffer overhead to allowfor the conversion to the I-frame. Evaluating the overhead needed forthe conversion includes, at least in part, a verification that availablebuffer levels relative to the picture to be converted are sufficientlyhigh to allow enough data to be extracted during a later decode.

The system can utilize data generated in verifying the various buffermodels (e.g., verifying through the process 520 of FIG. 5). Theverification data can further be used to determine amounts of headroomand/or overhead available for converting a P- or B-frame to an I-frame.One or more overhead thresholds can be employed to evaluate potentialcandidate start points such that the encoder incorporates one or morecontrol algorithms to anticipate overflowing the buffer, and ininstances where the processing and/or buffer levels are near maximumbuffer levels or within threshold limits of the maximum buffer levelsthe system avoids converting B- or P-frames to I-frames. As such, theseembodiments limit and/or avoid the need for the re-encode to be atrelatively low levels or bit rates that could result in poor quality.Some embodiments review one or more previous B-to-I frame size ratios toget a prediction of the change in picture size (bits) when convertingthe current B-frame to an I-frame. The predicted change in picture sizeis compared with the available space in the buffer. When there issufficient space, and usually an excess of space to provide a margin oferror, the system implements the change from the B- or P-frame to anI-frame and evaluates the buffer levels to determine whether the levelshave been exceeded. When the levels are exceeded a segment re-encode canbe performed to adjust the size or the conversion is not utilized.Alternatively, instead of predicting the change is picture size, someembodiments implement the conversion from B- or P-frame to an I-frameand then evaluate the buffer size to determine whether a failure occursand/or re-encoded is to be performed.

In implementing the re-encode and incorporating the re-encodedsegment(s) into the main content, some embodiments evaluate a buffermodel to determine whether valid re-encodes can be implemented atdesired segments and/or whether buffer models can be adjusted to allowfor the desired re-encoding while still satisfying model standardsand/or specifications.

FIG. 9 depicts a simplified flow diagram of a process 920 for use indetermining and implementing buffer model evaluations relative to are-encode. In step 922, the process parses the content stream (e.g.,during a base or initial encoding) and identifies parameters and/ormeta-data used in a buffer model analysis and simulation. In step 924,buffer model processing is implemented that includes a simulation ofbuffer model operation (e.g., effects on the buffer due in part tochanges in bit-rate or buffer size) and/or in merging of parametersand/or meta-data of the re-encoded segment and the content stream. Instep 926, one or more buffer model fields are corrected in the stream.

Buffers can be modeled according to “leaky” bucket models. A leakybucket model can, in some instances, be characterized by threeparameters a transmission bit rate (R), a bucket size or decoder buffersize (B) and a buffer fullness (F). In some implementations thetransmission bit rate R can be based on a peak transmission bit rate (inbits per second) when bits enter the decoder buffer. In constant bitrate (CBR) scenarios, the bit rate R is often the channel bit rateand/or the average bit rate of a video, video segment or video clip. Thesize of the bucket B or decoder buffer (in bits), which can smooth bitrate fluctuations, typically is maintained at a level less than aphysical buffer of an expected decoding device. The buffer fullness Fcan be defined by an initial decoder buffer fullness (in bits) before adecoder starts removing bits from the buffer. In some instances, aninitial start-up delay (D) can be defined by the fullness F and bit rateR where the delay D=F/R seconds.

FIG. 10 shows a simplified graphical representation of a leaky bucketmodel 1020. Typically in a leaky bucket model, bits enter a buffer atrate R represented by a slope 1022 until a level of fullness F 1024, andthen an initial number of bits b(0) 1026 for a first frame are removedat a time t1. The bits continue to enter the buffer at the bit rate R. Adecoder continues to remove bits b(1) 1030, b(2) 1032, . . . b(n−1),b(n) 1034 for subsequent frames at given time instants (e.g., t2, t3, .. . tn, respectively). Typically in a system providing constant bit rate(CBR), the slopes 1022 are substantially equal representative of theconstant bit rate with a fixed predetermined rate during data transfer.With variable bit rates (VBR), many systems operate by supplying contentat substantially a maximum rate until the buffer fills, and then waitsto resume filling, in some instances following a removal of bits fromthe buffer.

FIG. 11 shows a simplified graphical representation of a leaky bucketmodel 1120 according to a variable bit rate. The bits are supplied atabout the maximum fill rate represented by a slope 1122. The bits aresupplied at the rate until the buffer is full 1124. During a period1126, bits are not supplied to the buffer. Following the removal of bitsat 1130 bits are again supplied to the buffer at substantially themaximum rate.

In implementing the parsing phase 922 of the process 920, someembodiments identify, collect and/or extract parameters or data aboutthe content stream. Based at least in part on the parameters a leakybuffer model can be represented, for example, by the followingstructure, referred to below as “bufferModel”:

-   -   autc: Access unit time increment (invert frame rate);    -   bitrate: Bits stream rate specify the coded data is supplied to        the input of the HRD;    -   vbvsize: Size of the HRD buffer;    -   iscbr: Flag indicating CBR stream; and/or    -   lowdelay: Flag indicating low delay mode.        The lowdelay flag indicates (e.g., when set to “1”) that the        sequence does not contain B-pictures, that the frame reordering        delay is not present in the video buffering verifier (VBV)        description, and/or that the bit stream may contain “big        pictures”, where decoding a picture at the normally expected        time might cause a VBV buffer to underflow.

In some implementations when applied, for example, with AVC and/or VC1,a stream can have multiple leaky buffer models. An encoder can create avideo bit stream that is contained by some desired leaky buckets, or itcan simply compute the sets of parameters after the bit stream has beengenerated. During the parsing process, the following information can becollected for each access unit: the picture size, the picture type, thepicture position, the timing information and/or some informationspecific for each codec. Based on the information identified throughparsing and on the leaky buffer model, a value of the buffer level foreach access unit can be determined or computed. In some embodiments, theparsed information retrieved and/or a buffering level can be defined byone or more of, but not limited to, the following structure:

-   -   t_(ai): Arrival time of first bits from the access unit;    -   t_(af): Final arrival time of the last bits from the access        unit;    -   t_(rn): Removal time of the access unit from the buffer;    -   t_(on): Display time of the access unit;    -   preBufferLevel: Buffer level at the removal time prior to        removal;    -   ausize: Size of the access unit;    -   maxBufferLevel: Maximum buffer level found at this removal time;    -   minBufferLevel: Minimum buffer level found at this removal time;    -   unboundBufferLevel: Buffer level that is not restricted to the        buffer size (buffer level with an infinite buffer size); and/or    -   other relevant information.        Additional or alternative information can be defined that may be        specific, for example, to AVC. Such additional information may        include but is not limited to:    -   isbperiod: Flag indicating if it is a buffering period (GOVU        start);    -   initial_cpb_removal_delay: Pre decoding delay for the particular        removal time;    -   initial_cpb_removal_delay_offset: Pre decoding delay offset for        the particular removal time; and/or    -   calc_initial_cpb_removal_delay: Calculated value of an ideal pre        decoding delay for the particular removal time.        Further or alternative information can be defined that may be        specific, for example, to MPEG. Such additional information may        include but is not limited to:    -   isgovu: Flag indicating a new GOP;    -   vbv_delay: Indicate the buffer fullness for each picture in case        of CBR; and/or    -   calc_vbv_delay: Ideal value of the buffer fullness for each        picture.        Additional or alternative information can be defined that may be        specific, for example, to VC1. Such additional information may        include but is not limited to:    -   isgovu: Flag indicating a new entry point;    -   hrd_full: Indicate the buffer fullness for each picture; and/or    -   calc_hdr_full: Ideal value of the buffer fullness for each        picture.        For the access units, some embodiments can calculate the value        of the buffer fullness that the stream should indicate, e.g.,        vbv_delay in case of MPEG, hdr_full for VC1 and        initial_cpb_removal_delay in case of AVC.

Through the parsing process 922, a vector is generated of informationfor the access unit (e.g., vector of AVCAUInfo in the case of AVC), Nleaky buffering models (where N is the number of leaky buffering modelsspecified in the parsed stream), and for each of those models acorresponding vector of buffering level (e.g., vector ofAVCAUbufferLevel in the case of AVC). The information, parameters and/ormeta-data identified through parsing can additionally and/oralternatively be use to simulate one or more new buffering models bychanging the transmission rate and/or the buffer size parameters for agiven bit stream, or when performing a segment re-encode to maintain avalid buffer model.

Utilizing the parameters, information and/or meta-data identifiedthrough parsing, one or more leaky buffer models can be simulatedallowing the creation of one or more new valid buffer models that can beapplied to a particular stream. The simulation 924, in some embodiments,is used in part to change the bit-rate, buffer size and/or the bit-ratemode (e.g., VBR/CBR). For example, simulation in the case of AVC can bedescribed as follows:

static bool SimulateAUBuffer(

-   -   , const std::vector<AdvMux::AVCAUInfo>& auBaseList    -   , const std::vector<MPEGSystemStreamParser::AVCAUbufferLevel>&        auBaseBuffer    -   , bufferModel& model    -   , std::vector<MPEGSystemStreamParser::AVCAUbufferLevel>&        auOutBuffer);        Each simulation identifies when one or more buffer thresholds        are exceeded, such as overflow thresholds and/or underflow        thresholds, and returns the results, such as returning the        result of the number of overflows and underflows detected in the        bufferModel structure and/or a vector of buffer levels over a        stream and/or segment. When a simulation succeeds without        overflows or underflows, the stream can be modified based on the        new bufferModel passed in above during a stream correction phase        as further described below. Some implementations further        attempts to improve buffer re-analysis, for example with VC1 and        MPEG2, that allow the re-analysis to be halted when newly        determined values match values from the base encode. Further in        some embodiments, the buffer analysis is simplified by analyzing        the information, parameters and/or meta-data and typically does        not have to read an entire stream from disk and parse the data.

The correction phase 926, in part, consists in some embodiments of therewriting of fields in order to correct or replace a leaky buffer modelspecified in a base encode that is identified as no longer being valid.The stream is altered to conform to a new model that comes from asimulation and/or the merging processing 924 in the case of segmentre-encode as described above and further described below. The correctionphase performs, in part, a rewrite of one or more fields. For example,with MPEG-2, the correction phase can cause a rewrite of one or more ofthe following fields:

-   -   bit_rate_value and bit_rate_extension: The new value of the        bit-rate;    -   vbv_buffer_size_value and vbv_buffer_size_extension: The new        value of the buffer size; and/or    -   vbv_delay: The new value of the buffer fullness of each picture.        Similarly, with VC1 correction phase can cause an additional or        alterative rewriting of one or more of the following fields:    -   hrd_rate[n]: The new value of the bit-rate for this particular        leaky buffer model;    -   hrd_buffer[n]: The new value of the buffer size for this        particular leaky buffer model; and/or    -   hrd_full[n]: The new value of the buffer fullness of each        picture for this particular leaky buffer model.        Still further with regard to AVC, the correction phase can cause        an additional or alterative rewrite of one or more of the        following fields:    -   bit_rate_value_minus1[n]: The new value of the bit-rate for this        particular leaky buffer model;    -   cpb_size_value_minus1[n]: The new value of the buffer size for        this particular leaky buffer model;    -   cbr_flag[n]: The new value of the CBR/VBR flag for this        particular leaky buffer model;    -   initial_cpb_removal_delay[n]: The new value of the decoding        delay for this particular leaky buffer model; and/or    -   initial_cpb removal_delay_offset[n]: The new value of the        decoding delay offset for this particular leaky buffer model.        A new value of the initial_cpb_removal_delay can correspond with        a preferred or ideal value calc_initial_cpb_removal_delay store        in a buffering level vector. The value of        calc_initial_cpb_removal_delay can be calculated, according to        some implementations, as follows:        calc_initial_cpb_removal_delay=tg,90_((n))=90000*(tr,n _((n))        −taf _((n-1))),        where the constraint for VBR of        initial_cpb_removal_delay<=Ceil(Δtg,90_((n))) is followed,        and/or the constraint for CBR of        Floor(Δtg,90_((n)))<=initial_cpb_removal_delay<=Ceil(Δtg,90_((n)))        is followed.

The segment based re-encoding, at least in part, allows the re-encodingof a section of video, for example, to increase the quality of a segmentthat does not meet visual quality standards. The increased quality canbe achieved, for example, by increasing the bit rate of the segment.Segment based re-encoding can additionally and/or alternatively beemployed, for example, to reduce the number of bits utilized in asegment to provide extra bits to other segments or sections of thestream. In some embodiments, it is beneficial to determine a maximum bitrate that can be utilized and/or specified by a user for a given segmentthat can substantially avoid underflows and/or overflows downstream dueto the changes. Prior to a segment re-encode, bit-rate boundaries andthe buffer fullness boundaries can be determined that result in a legalstream. For example, the boundaries can be determined as follows:

static bool bitrateBoundaryAUBuffer(

-   -   const UInt32 segIndex    -   , const UInt32 segSize    -   , const bufferModel& model    -   , const std::vector<AdvMux::AVCAUInfo>& auList    -   , const std::vector<MPEGSystemStreamParser::AVCAUbufferLevel>&        auBuffer    -   , double& minimumBitrate    -   , double& maximumBitrate    -   , double& minimumBufferFullness    -   , double& maximumBufferFullness).        The minimumBitrate corresponds to a rate in CBR with no        overflow; the maximumBitrate corresponds to a rate with no        underflow; the minimumBufferFullness corresponds to the target        minimum buffer fullness in bits with no underflow; and the        maximumBufferFullness corresponds to the target maximum buffer        fullness in bits with no overflow.

In some embodiments when calculating a maximum bit rate that can beallowed for a segment re-encode, a buffer model simulation is performedwith, for example, an infinitely sized buffer in the case of MPEG-2and/or VC1, and no constraint arrival time leaky bucket model (CAT-LB)constraint in AVC. Applying these constraints substantially eliminatesbit-rate zeroed flat sections in the buffer level graphs, and the bufferlevels are unbounded by buffer size or CAT-LB constraints. The value ofunboundedBufferLevel in the buffer level structure corresponds to thisunbound buffer level. A search can then be performed for the minimum“unbounded” buffer level resulting from this buffer model simulationstarting from the first picture after the end of a segment re-encode andending with the end of stream or other ending point (e.g., in someinstances, the end point can be at a flat section 1126). The unboundedlevel is referred to below as unboundedBufferLevelb_((Min)).Additionally, a maximum of unboundBufferLevel can be determinedconsidering values starting from the first picture after the re-encodesegment and ending with the end of the stream or other end point, wherethis value is referred to below as unboundBufferLevelb_((Max)). Based atleast in part on the unboundedBufferLevelb_((Min)) andunboundBufferLevelb_((Max)), a change in minimum and maximum levels canbe determined, for example, as follows:DeltaLevelMin=(unboundBufferLevelb_((Min))−unboundBufferLevel_((n))+preBufferLevel_((n)));and/orDeltaLevelMax=max((unboundBufferLevelb_((Max))−unboundBufferLevel_((n))+preBufferLevel_((n))),B),where unboundBufferLevel_((n)) is the value of the unboundBufferLevel ofthe first picture to re-encode and preBufferLevel_((n)) is the value ofthe preBufferLevel of the first picture to re-encode. With Rrepresenting an actual rate of the stream, B representing a size of thebuffer and segLen representing the length in seconds of the segment tore-encode, a maximum bit-rate can be calculated in some implementationsas follows:maxBitrate=R+DeltaLevelMin/segLen.

The minimum buffer level can be determined by subtracting theDeltaLevelMin value from the buffer fullness, after removal of the lastpicture of the base encode (with the value clipped to >=0). Thiseffectively results in a shifting in an amount of buffer availabilityand effectively shifts the graph (e.g., graph 1020) down by about theminimum buffer level in attempts to avoid an underflow of the buffer.Similarly, the minimum bit-rate in CBR can correspond tominBitrate=R−DeltaLevelMax/segLen and in some instances is zero (0) forVBR. A maximum buffer level in CBR can be defined as the addition of(B−unboundBufferLevelb_((Max))) with the buffer fullness, after removalof the last picture of the base encode (with the value clipped to >=0).This effectively shifts the graph up by an amount in attempts to avoidan overflow of the buffer.

In some implementations, following a segment re-encode, merging 924 isperformed that merges the buffer level and the access unit informationfrom the base encode with the re-encoded segment encode data. Themerging at least in part attempts to keep the buffer model valid duringand/or following the re-encoded segment. An example of a merging processfor at least AVC can be described as follow:

static bool MergeAUBuffer(

-   -   const UInt32 mergeIndex    -   , const std::vector<AdvMux::AVCAUInfo>& auBaseList    -   , const std::vector<MPEGSystemStreamParser::AVCAUbufferLevel>&        auBaseBuffer    -   , const std::vector<AdvMux::AVCAUInfo>& auSegList    -   , const std::vector<MPEGSystemStreamParser::AVCAUbufferModel>&        auSegBuffer    -   , bufferModel& model    -   , std::vector<AdvMux::AVCAUInfo>& auOutList    -   , std::vector<MPEGSystemStreamParser::AVCAUbufferModel>&        auOutBuffer)        Where the arguments can be defined as follow:    -   mergeIndex: Merging index;    -   auBaseList: Base list of access unit information;    -   auBaseBuffer: Base list of buffer level;    -   auSegList: Segment list of access unit information;    -   auSegBuffer: Segment list of buffer level;    -   model: Buffer model in used;    -   auOutList: Output list of access unit information; and    -   auOutBuffer: Output list of buffer level.

The merging process returns a resulting number of overflows and/orunderflows. The output values generated by the merging process can besubsequently used as a new base encode for the subsequent segmentre-encode. If a merge succeeds with no overflows and no underflows, thestream buffer fullness information can be used during a correction phase926 to correct the stream.

The merging process is performed, in some implementations, for eachsegment re-encode for each leaky buffer model present in a stream, whichis not necessarily unique in the case of AVC and VC1. In instances wherethere are multiple leaky buffer models present in the stream, it ispossible that one or more models can be invalidated, for example, due tothe presence of underflow or overflow. In some embodiments, an invalidmodel is designated as invalid and/or replaced by a buffer model that isknown to be valid for the stream. For example, the buffer vector and/orother parameters or meta-data (e.g., buffer size, bit rate, bufferfullness, and/or other data) for the failed model can be replaced byparameters and/or meta-data of a valid model. Additionally and/oralternatively, as described above, one or more invalid buffer models canbe altered so that the model can be validated. The altering of the modelmaintains the model within give specifications (e.g., high definitionDVD (HD-DVD), Blu-ray disc (BD), and/or other specification) but altersthe model from initially defined parameters (e.g., user specifiedparameters, such as parameters to account for multiplexing of streams).The altering of the models can, in some instances, reduce the number ofre-encodes that are performed while still meeting the altered buffermodel.

Some embodiments further allow dummy or place holder buffer models thatallow for performing post analysis and providing more valid models. Themodels can be built or specified later based on the parsing that wasperformed during the base encode and/or segment re-encodes. This allowssubstantially any number of models to be defined that can replace theplace holder models.

Further, some embodiments perform a preprocessing that identifies priorto a segment re-encode an amount of additional buffer availability thatcan be utilized by effectively utilizing a margin above an underflowand/or a margin below an overflow. Referring again to FIG. 10, as thebuffer cycles through a filling and releasing of bits, the fill levelapproaches a lower or zero level 1040. The smallest distance 1042between the fill level and the minimum buffer level can be identified,in some implementations, as a margin of buffer availability. Asintroduced above, some embodiments provide for a shifting in an amountof buffer availability and effectively shifts the graph down by aboutthe margin of availability in attempts to provide increased bufferutilization while avoiding an underflow and/or overflow of the buffer.In utilizing the minimum margin, underflows typically are avoided. Someembodiments perform a further or subsequent simulation to determinewhether the shift causes any under or overflows.

Similar use of available buffer margins can be employed with variablebit rate (VBR) encoding. Referring to FIG. 11, again the minimum marginbetween the fill level and the lower or zero levels can be identified.With VBR, however, following a shift, once the fill level reaches themaximum fill 1126 and stops accepting bits, the shift is effectivelyeliminated, and the buffer model continues as if there was no shift. Assuch, some embodiments allow multiple shifts along the stream and theminimum margin is determined between maximum fill levels (e.g., flatareas 1126). The amount of available buffer shift is determined, in someembodiments, through the simulation process 924. In someimplementations, the determination of available shift is implementedprior to performing segment re-encodes to more fully utilize the buffer.The simulations can be performed for each of the buffer models when morethan one model is identified.

As introduced above, some embodiments allow a user to control theencoding and/or re-encode, providing the user with greater control overthe encoding process and greater satisfaction of the encoded endproduct. For example, the system can identify one or more segments thatfail a model, identify a plurality of possible P- and/or B-pictures tothe user from which to select where a new I-frame is to be generatedand/or other such feedback and information. The user can then selectwhich frame is to be converted, which segment(s) to re-encode or performother functions.

FIG. 12 shows a graphical user interface 1220 according to someembodiments that facilitates and/or allows a user to encode content,review encoded content and/or to implement and control re-encoding ofone or more segments. The user interface can be generated through acomputer or other relevant devices, and in some embodiments the encodingsystem 124 is implemented through a computer that also generates anddisplays the user interface 1220. The user interface 1220 includes asettings window 1222, a source code control window 1224, a playback ormovie control window 1226, a preview window 1230, a timeline window1232, and a user interface tool bar 1234. In some implementations, thetimeline window 1232 is not depicted within the user interface 1220until the content being evaluated has been encoded through a base orinitial encoding. The timeline window can further identify one or moresegments 1250, 1252, 1254, 1254 that have been highlighted, selected,identified to be re-encoded and/or re-encoded as further describedbelow.

FIG. 13 depicts a simplified graphical representation of the source codecontrol window 1224. The source code control window allows a user todefine and access a source of content to be encoded and can be accessedand selections made using a keyboard, a mouse, stylists, remote controlor other pointing device and/or other such methods. Further, the sourcecontrol window includes several options, keys and/or buttons such asplay 1322, stop 1324, rewind 1326, fast forward 1328, loop play 1330,variable speed playback 1332, nudge previous and/or next entry point1334 and/or other such buttons; a shuttle control bar 1336; a variablespeed control drag bar 1340; a monitor control 1342; location Aindicator 1344; location B indicator 1346; timecode display 1350;indicators such as frame drop 1352, synch mode 1354 and other suchindicators; and/or other options, features and/or buttons. Using thesource control window a user can in part find start and end points formaterial to be encoded.

The shuttle control 1336 shuttles back and forth to nearby locations.The further left (e.g., representing back) or right (e.g., representingforward) the shuttle control is dragged, the faster it locates, and canbe effectively biased to return to a predefined point, such as thecenter when released. The nudge buttons 1334 allow navigation throughthe content one entry point at a time. The “locate A” 1344 stores andrecalls a timecode location for the source material and “locate B” 1348stores and recalls a timecode location for the source material. Thetimecode display 1348 shows the current timecode location for the sourcematerial. The sync status 1354 indicates whether sync mode is enabledallowing the movie control window 1226 to stay in sync with playbackfrom the source control window 1224. The frame drop 1352 indicates whenframes are dropped during source playback. The monitor control 1342toggles which transport is the active one (source control window 1224 ormovie control window 1226).

FIG. 14 depicts a simplified graphical representation of the moviecontrol window 1226. The movie control window allows a user to previewencoded content and can be accessed and selections made using akeyboard, a mouse, stylists, remote control or other pointing deviceand/or other such methods. Further, the movie control window includesseveral buttons, indicators, control bars, time display and the like,and in some implementations these buttons, indicators and the like aresimilar to those of the source control window 1224.

FIG. 15 shows a simplified graphical representation of the timelinewindow 1232 according to some embodiments. The timeline window includesa tool bar 1522, a bit rate track 1524, an entry points track 1526, apicture structure track 1530, a quality track 1532 such as a signal tonoise ratio (PSNR) track, a status bar 1534, time markers 1536, one ormore scroll bars 1540 and other relevant fields or areas. The timelinetool bar 1522 at least in part allows a user to navigate content andmark segments, and the status bar 1534 displays information about thesession. Typically, the bit rate track 1524, entry point track 1526,picture structure track 1530 and quality track 1532 are cooperatedand/or coordinated such that entries within each track correspond withentries in one or more of the other tracks. For example, someembodiments configure the tracks such that entry point track 1526,picture structure track 1530 and quality track 1532 correspond with thebit rate track 1524.

The timeline window 1232 includes tracks that display the content bitrate 1524, entry points 1526, picture structure 1530, and a measure ofquality 1532. Individual tracks can be set to their own height and theycan be hidden. In some embodiment, the timeline and/or track data can bezoomed to provide greater resolution. The bit rate track 1524 displays aplot of the bit rate for the video encoded content. In some instances,when the content is encoded with CBR the graph is generally level or astraight line, while when encoded with VBR the graph varies over time asthe bit rate varies, for example with each GOP. The minimum and maximumvalues for the plot differ depending on the encoder, target application(e.g., HD-DVD, Blu-ray or the like) and/or other such factors.

The entry points track 1526 displays the entry points in the content asvertical lines. Multiple types of entry points can be defined, and insome embodiments, at least two types of entry points can be displayed:“normal” (N) 1550 and “custom” (C) 1552, where the custom points can beuser defined points, such as chapter points and/or other points wherere-encodes are to be initiated or terminated. In many instances, thecustom entry points 1552 are specified in a list before the encode. Insome embodiments, when the timeline 1232 is zoomed in, numbers for thecustom entry points 1552 are also displayed. The entry points definevalid locations when scrubbing the playhead, setting segment re-encodein-points and out-points, locations for chapter points (e.g., whenauthoring HD-DVD content, Blu-ray content and/or other relevantcontent). Further, the entry points show in some instances GOP headerpoints, for example with MPEG showing where the I-frames are along thecontent stream, points where chapter point can be defined and/or otherpoints, for example, where start points for a re-encodes may be defined.The normal identifiers 1550, in some instances, can identify where scenechanges occur. In some embodiments, the re-encoding reconfigures framestructures allowing for the generation of a new I-frame and/or theconversion of a B or P-frame to and I frame. The entry points track 1526can, in some implementations, further identify those new and/orconverted I-frames.

The picture structure track 1530 can display, in some implementations,individual picture types in each GOP, for example, with vertical linesdistinguished by varying line heights (e.g., I-frames, tall lines;P-frames, medium lines; B-frames, short lines).

The timeline 1232 can further show the quality measure track 1532 thatin some implementations is PSNR track depicting a peak signal-to-noiseratio data. In some embodiments the PSNR track is a PSNR-Y track basedon luminance (Y). PSNR can be used to determine a quality of an encode,and can be determined in some embodiments by comparing luminanceintensities across the encoded image with those in the source content,or other signal-to-noise ratio calculations. Typically, the PSNR track1532 shows the PSNR for each GOP and/or frame of the encoded content.The PSNR values can aid a user in identifying one or more GOPs and/orframes that may not meet desired encoding results and/or picturequality, and segments to be re-encoded.

FIG. 16 depicts a simplified graphical representation of an enlargedview of the timeline toolbar 1522. The toolbar includes a number ofdifferent tools or features that can include a number of options,buttons, toggle switches, text and/or numeric fields, indicators,parameter information and/or substantially any other relevant tools. Insome embodiments, the timeline toolbar 1522 includes zoom-in andzoom-out tools 1622 and 1624, respectively; setting “in-points” tool1626 and “out-points” tool 1628; marking segments option 1630; clearsegment option 1632; previous segment option 1634; next segment option1636; adding the session to a batch encode options 1638; opening thetimeline display options dialog box tool 1640; and/or other relevantoptions and tools. The timeline toolbar 1522 also includes fields suchas playhead location field 1644, playhead bit rate field 1646, playheadPSNR field 1648, in-point and out-point location fields 1650, 1652,segment duration field 1654, segment bit rate field 1656, segment PSNRfield 1660 and/or other relevant fields.

FIG. 17 depicts a simplified graphical representation of an enlargedview of the status bar 1534. The status bar includes a plurality offields providing additional information and statistics to the user. Insome embodiments, the status bar 1534 includes a bit budget field 1722,bit budget meter and field 1724, total duration field 1726, average bitrate field 1730, average PSNR field 1732, video standard field 1734, alast save field 1736, and/or other such fields.

The bit budget field 1722 provides a target capacity, for example, ofvideo material in the content, and can include encoded content and othercontent or material that is to be re-encoded. A user can enter a valuedirectly into the field 1722. Additionally or alternatively, the fieldcan be automatically filled based on a default value that is equal to asize of the encoded content plus a defined headroom specified in adefault headroom option, which can be accessed in some embodimentsthrough the user interface toolbar 1234. For example, when the encodedcontent is 130 MB and the default headroom option is set to 20%, thedefault bit budget is approximately set at 157 MB (i.e., 130*1.2). Insome embodiments, a maximum value that can be entered directly into thebit budget field 1722 is determined by a target application (e.g.,30,000 MB for HD DVD-Video; 50,000 MB for Blue-ray; and other suchmaximums based on target applications).

The bit budget meter field 1724 displays a session's or project'sremaining and used space. Some implementations include a pull down ortoggle switch 1744 that can be selected or clicked with a selectiondevice, such as those described above or other such selection device, totoggle between a remaining and used space. The capacity for the sessionis displayed in the bit budget field 1722. The used space is calculated,in some embodiments, by adding the size of the encoded material plussegment re-encodes that are pending. In some embodiments, when a bitrate for a selected segment is changed, the bit budge field 1722 can beadjusted to show the user how much extra data will be used and/or neededif the re-encode were to be performed. Further, some embodiments providean options menu that can be activated to allow a user to specify anamount of headroom that is to be maintained for the bit budget forre-encodes. In some instances, the bit budget is defined as a percentagein excess of the base budget.

The total duration field 1726 displays an entire duration in hours,minutes, seconds, and frames of the content. The average bit rate field1730 displays the average bit rate for the content stream, and in someinstances, when one or more segments are pending re-encode (e.g.,selected for re-encoding but have not yet been re-encoded), thedetermination of the average bit rate is based on the bit rate valuesfrom the pending segments initial encode (e.g., not the selected pendingre-encoded bit rate).

The average PSNR field 1732 displays an average PSNR value for theentire content. In some embodiments, the PSNR is a luminance PSNR andthe average PSNR displays an average luminance PSNR value for the entirecontent stream; however, other signal to noise ratio values can be usedand/or define portions of the content (e.g., average PSNR for a segmentor other such portions). The values identified in the average bit ratefield 1730 and average PSNR field 1732 can be based on current averagesof a selected or highlighted segment, which typically differs from thevalues specified in the segments tab window listing when the bit ratefor the selected segment has been changed. The video standard field 1734displays the vertical resolution, scan mode, and frame rate for thecontent stream, and the last save field 1736 displays the date and timewhen the session was last saved.

The preview window 1230 of the user interface 1220 of FIG. 12 displaysthe content images and can be the source content or the encoded content.Once a re-encode is performed, a user can select a headend point (e.g.,using a point or the like) prior to the re-encoded segment and activatea playback so that the re-encoded segment is played back in the previewwindow 1230. In some embodiments as described above and further below,the data of the re-encoded segment is stored in a separate file than thebase encoded file and upon playing back of the re-encoded segment, theseparate file is accessed for playback. Further, the user can activatethe preview window to be full screen or substantially any desired size.In some implementations, the preview window can be displayed on aseparate display or monitor allowing a larger or full screen view whilestill allowing the user to utilize the other windows of the userinterface 1220.

FIGS. 18-21 depict various options within the settings window 1222. Morespecifically, the settings window includes one or more tabs or otherselection buttons 1822 that allow a user to access the various optionsavailable through the settings window. In some embodiments, the tabs1822 can include an inputs tab 1824, a video tab 1826, a segments tab1828, an express or expressQC tab 1830, and/or other such tabs.

The input tab when selected prior to encoding access an input settingswindow that allows a user to access and adjust settings and parametersand to view statistics defining some of the parameters settingsfollowing a base encode of the content. The video source can consist ofsingle video files, an image sequence folder and/or other relevantsources. Information about the source material is displayed in asettings summary box. Before the encode, the input tab settings windowhas an edit settings button that opens an input file settings dialogbox, where a user can configure settings for the video source material.In some embodiments, the input settings window allows the setting of avideo source type (e.g., setting the source type to one of a file,multiple video frame files (an image sequence), and/or other sourcetypes); add media where parameter fields can be updated with values readfrom the media file and specify values for any parameters not determinedfrom the media, where a pixel format specifies a data structure of theRGB or YUV video samples; specify source start timecode; repeating aprevious step to add additional media files; removing one or more mediafiles; browse to a different source; and/or other settings orparameters.

FIG. 18 shows the settings window 1222 with the input tab settingswindow 1820 displayed following a base encode. The input tab windowdisplays a summary of the parameters actually used during the baseencode. For example, the input tab window may show the source file 1840,and parameters of the source file and/or parameters used duringencoding, such as resolution, scan mode, timecoder, pixel format andsubstantially any other relevant parameter.

The video tab 1826 activates a video tab settings window 1920 allowing auser to access settings for the video encoding parameters. Before anencoding, the video tab settings window can include a settings pop-upmenu for recalling video presets and default settings. The settingspop-up menu also can contain an edit command that opens a video settingsdialog box, where the video encoding parameters can be configured andsaved.

FIG. 19 depicts the settings window 1222 with the video tab settingswindow 1920 displayed following a base encode. Following an encode, thevideo tab window shows parameters utilized during encoding, such ascodec, encoder, profile, level, resolution, picture structure, framerate, display aspect ratio, target application, bit rate parameters,control mode, pass count, target bit rate, maximum bit rate, picturestructure, scene detection, IDR interval, minimum IDR interval, Bframes, dynamic B-frame placement, use pyramid B-frame structure, motionsearch, number reference frames, subpixel accuracy, intra search shapes,inter search shapes, rate distortion optimization, hadamard transform,multiple reference frame, sub-block, intra-frame, entrop encoding mode,in loop deblocking filter flag, Cb quantize offset, Cr quantize offset,alpha filter offset, beta filter offset, other parameters for otherencoding schemes (e.g., MPEG2, AVC, VC1 and/or other such schemes) andsubstantially any other relevant parameters.

FIG. 20 depicts the settings window 1222 with the segments tab settingswindow 2020 displayed. The segments tab settings window displaysinformation about selected, highlighted, and/or re-encoded segments ofthe session and can include controls for setting bit rates for one ormore re-encodes for selected segments. In some embodiments, the selectedsegments are identified by start and end points 2022 and 2024 (typicallylisted as a time relative to the timeline of the content). Further, thesegments tab settings window can specify a new re-encode bit rate 2026for each segment, and a status 2030 of the segment (e.g., “marked”identifying a segment highlighted but where the bit rate has yet to beset or altered; “pending” being a selected segment with a bit ratechanged and not yet re-encoded; “done” being a segment that has beenre-encoded according to the altered bit rate and/or other suchidentifiers). The segments can be sorted by clicking the column heads2032 and the columns can be resized by dragging the column dividers.

In some embodiments, the segments tab settings window 2020 includes asegment bit rate area 2040 that allows a user to enter a bit rate valuein a bit rate value field 2042. The bit rate value can further bequantified by an edit mode 2044 defined as an “absolute” segment,relative segment, and/or other such definition. In some implementations,the absolute segments can be re-encoded at an absolute bit rate asspecified in the bit rate value field 2042. When editing multiplesegments at an absolute bit rate, the new bit rates typically aresubstantially the same for each of the segments. The relative segmentscan be re-encoded at a relative bit rate, where the existing bit rate isincreased by a value specified in the bit rate value field 2042. Forexample, if three segments with bit rates of 4.0, 4.5, and 5.1 Mbps arere-encoded with a relative bit rate of +1.5 Mbps, the new bit rates willbe 5.5, 6.0, and 6.6 Mbps, respectively. Additionally or alternatively,a user can use the bit rate drag bar 2046 with the bit rate value in thebit rate value field 2042 changing as the bar is dragged. In someimplementations, a maximum and minimum bit rate values can be displayed,that are representative of maximum and minimum values availableaccording to a decoder model (typically previously set), maximum andminimum values of the base encode or other relevant maximum and minimumvalues. Once the adjusted bit rate for the re-encode is selected (e.g.,by entering it directly into the bit rate field 2042, by adjusting thebit rate drag bar 2046, moving an average bit rate indicator on thetimeline 1232 and/or other such entries), the bit rate for the re-encodeis reflected in the bit rate column 2026 and the status for the selectedsegments changes, for example, to pending. In some embodiments, pendingsegments are identified or distinguished in the timeline window 1232 bya highlighting, a different color or the like, and in some instancesshow the pending bit rate in the timeline window.

FIG. 21 depicts the settings window 1222 with the expressQC tab settingswindow 2120 displayed. The expressQC tab settings window is available atleast after an encode and provides controls that can be use to selectsegments for re-encoding, for example, based on a quality measure, suchas PSNR statistics. In some embodiments, the expressQC tab settingswindow 2120 includes detection mode parameters 2122 and segment lengthparameters 2124. The detection mode parameters can include a PSNRthreshold option 2128, threshold level field 2130 and/or threshold leveldrag bar 2132; and/or a number of segments option 2134, a number ofsegments threshold field 2136 and/or number of segments drag bar 2138.

The segment length parameters can include a minimum GOPs length field2140 and a GOPs length drag bar 2142. A mark segment option or button2144 is further included to initiate a search or evaluation of thecontent and to mark one or more segments throughout the content orselected portion of the content that have a defined relationship withrespect to the thresholds and/or levels specified by the detection modeparameters 2122 and/or segment length parameters 2124. For example, whenidentifying segments with PSNR levels below a threshold, these segmentsare quickly located and highlighted on the timeline window 1232 (e.g.,see FIG. 12 showing three segments 1250, 1252, and 1254 selected). Theuser interface 1220 further allows a user to unselect one or moresegments marked through the automated process using the expressQCparameters and/or thresholds.

Additionally or alternatively, the timeline 1232 can be used to selectand/or define selected segments. In some embodiments, a user positionsor drags an indicator to identify one or more areas of the encodedcontent. Referring to FIGS. 12, 15-16 and 20-21, a user can select oneor more segments that include the unsatisfactory portion using thein-point tool 1626 and out-point tool 1628 to position an in-marker oridentifier 1260 and out-identifier 1262 bounding a segment 1254 ofinterest. A user can place the identifiers by dragging the identifiersto the desired locations. In some embodiments, the precise placement ofthe identifiers can be adjusted by the system relative to a positioningselected by the user. The adjustment can be based on an evaluation ofthe segment(s) within the selected region bounded between the in- andout-identifiers and/or the content downstream. The adjustment to the in-and out-points to define start and stop points for the re-encode isfurther described below and can be adjusted based on many factorsincluding a determination of appropriate re-encode start and stoppoints, dependency between frames and other such factors.

In some implementations, a currently selected segment(s) bounded by thein- and out-identifiers 1260, 1262 is highlighted with a firsthighlighting (e.g., different color, cross-hatching, dashed lines,brightness and/or other such distinguishing characteristics). Othersegments can be identified with alternate highlighting, for example,those segments that have already been re-encoded, for example fourthsegment 1256, can be identified with a secondary highlighting (e.g.,secondary color), marked segments can have a third highlighting (e.g.,third color), and/or pending segments can have a fourth highlighting(e.g., fourth color).

As described above, the bit rate graph 1524 showing an average bit ratevalue for each GOP 1560. The timeline tool bar 1522 also shows the valueof the play position average bit rate 1646 at the position of theplayhead (e.g., for the identified, highlighted and/or selected GOP). Asthe playhead is moved, for example using a pointer device such as amouse to drag the playhead indicator, the value of the bit rate in theplay position average bit rate field 1646 changes.

In some embodiments, the timeline further includes a segment bit ratebar 1570 for those segments selected and/or highlighted. The segment bitrate bar or indication initially identifies an average bit rate for theselected segment. Users can utilize the segment bit rate bar 1570 tochange the desired average bit rate for the selected segment by draggingthe bar (e.g., using a pointer device) to a desired bit rate. Someembodiments further display the selected segment bit rate 1572associated with the position of the segment bit rate bar 1570 andchanges as the bar is moved. Additionally or alternatively as describedabove, a user can utilize the segment bit rate area 2040 of the segmentstab settings window 2020 to enter a bit rate value in a bit rate valuefield 2042 or the bit rate drag bar 2046.

The user interface 1232 further allows a user to activate a re-encode ofone or more pending and/or marked segments. In some embodiments,multiple segments can be selected at a time. Upon activation of asegment re-encode a progress window may appear notifying the user of theprogress of the re-encode. In instances where a user attempts to alterthe bit rate beyond a limit that will cause an underflow or overflow ofthe buffer, an error or warning indicator can be displayed. In someinstances, this warning indicator is generated prior to a re-encodebeing attempted based on a pre-analysis of the segment, the altered bitrate, the downstream content and/or the buffer model. An error messagecan be generated in some instances upon attempting a re-encodeindicating that the re-encode may result in an overflow or underflow. Asintroduce above, however, some embodiments further allow for theadjustment and/or compensation for bit rate changes to reduce potentialerrors by adjusting bit rates and/or buffer levels down stream from theselected segment and/or in neighboring segments to the selected segment.

In some implementations, the user interface 1220 allows a user to adjustthe bit rate for a selected segment between the maximum and minimum bitrates set for the model. Some embodiments, however, calculate themaximum and/or minimum available bit rates by analyzing the contentand/or meta-data downstream from the selected segment that may beavailable for the re-encode of the selected segment. This providesfurther feedback to the user regarding what they can actually achieveand whether further re-encodes of neighboring and/or other segments areneeded to free up additional bits.

There is substantially no limit as to the number of segments that can bemarked and/or selected at a give time. As such, a user can mark multiplesegments and make iterative adjustments to the multiple segments toachieve a desired bit rate for a segment with a higher priority. Forexample, a user can select a first segments 1250 as well as second andthird segments 1252, 1254 downstream of the first segment, and makeadjustments to the second and third segments to free up bits for thefirst segment, which can be reflected by an indication of a change in amaximum available bit rate for the first segment as the bit rates forthe second and/or third segments are adjusted.

Once the user has completed the desired re-encoding, the user canactivate a finalization through the user interface 1220. Thefinalization merges the segment re-encodes with the base encodes andupdates the data of the stream for the buffer levels as fully describedabove and further below. In some embodiments, the user interface 1220may include an additional segments edited tab in the settings window1222 that allow a user to define and/or alter parameters, such as atarget bit rate, minimum or floor bit rate, quantization offset ofchrominance, in loop deblocking filter or other filtering, buffer size,buffer fullness levels and/or other such relevant parameters. Theseparameters may vary depending on the specified codec being applied.Additionally and/or alternatively, some embodiments allow a user toselect a specific frame, for example through the time line 1232, anddefining a change in picture type (e.g., by using a drop down window,dragging it to a picture frame type indicator and/or other suchactivation), such as promoting a B- or P-frame to an I-frame. Thispromotion of frame types can be used, for example, for marking a scenechange (e.g., when the scene detection system fails to accurately detecta scene change).

The zoom-in option 1622 and zoom-out option 1624 provide zoomingcapabilities on the timeline tracks. The timeline 1232 depicted in FIG.15 is a zoomed-in view of the portion of the timeline 1232 labeled byreference numeral 1240 showing greater precision along the portion 1240of the timeline. This zooming allows a user to view a timeline relativeto a large portion or all of the content while additionally providinggreater access to more precise data, and further provides a user withmore precise control over the identification and/or selection of framesand/or segments, as well as more accurate evaluation of the encodedstream and PSNR data of the PSNR track 1532.

Referring to FIGS. 12 and 15, the GOPs of the portion 1240 are zoomed inand expanded in FIG. 15 (e.g., showing approximately 11 full GOPs inthis view). The bit rate track 1524 graphically depicts approximateaverage bit rates 1562 over each GOP. Further, a user can moreaccurately identify the normal entry points 1550 and custom entry points1552 depicted along the entry point track 1526, as well as the picturetypes depicted along the picture structure track 1530. As describedabove, a user can select a segment and use the segment bit rate bar 1570to set a desired bit rate for re-encode.

In implementing the encoding and/or segment re-encoding, someembodiments employ an encoding process and/or encoder system that allowsfor accelerated encoding rates resulting in reduced processing time. Asthe amount of data supplied with respect to some content, such as highdefinition content and/or other content containing large amounts ofdata, the data rates can be extreme and typically the resulting outputquality needs can be very high. Thus, the processing requirements forencoding some content can be great. Some present embodiments providehigh quality encoded content at relatively high data rates, such asencoding at about real time rates, by in part temporally breaking orslicing the unencoded content and providing parallel encoding,effectively scaling up processing to achieve a desired encoding rate.The parallel encoding increases the speed at which the content isencoded and/or allows enhanced or more precise encoding without undueadditional processing time.

FIG. 22 depicts a simplified block diagram of an encoding system 2220according to some embodiments. The encoding system includes a dicer ordivider 2222, a plurality of dicer buffers 2224-2226, a plurality ofencoding processor units 2230-2232, a splicer or concatenator 2236, anda host controller 2238. In operation unencoded content 2240, for examplehigh definition digital content, is supplied to the dicer 2222. Thedicer determines how to divide the content, divides the content andforwards the divided segments 2242 to one of the dicer buffers2224-2226. The dicer can be implemented as hardware, software, firmwareand/or a combination, and can be operated in some instances from acomputer, such as the host computer.

The divided segments consist of a sequence of frames that are deliveredto the encoding processor units 2230-2232 through the buffers and theencoding processor units encode the content. The divided groups ofsegments can be forwarded to the buffers and/or encoding processor unitsthrough firewire connections, hardware specific connections, Ethernet,one or more buses (e.g., peripheral component interconnect, PCI) and/orother connections. The encoding processing units 2230-2232 can beimplemented through hardware, software, firmware and/or a combinationthereof, which can be implemented on a single processor, singlecomputer, a plurality of processors and/or computers, individual digitalsignal processor (DSP), arrays of DSPs, and/or other devices orcombinations of devices. In some embodiments, the encoding processorunits are operated from one or more processors and/or computers withstripped down and/or simplified operating systems reducing processingoverhead, improving processing speed and reducing complexity.

The encoded divided segments 2244 are then supplied to the splicer 2236,for example over Ethernet, PCI bus or other relevant communicationlink(s). The splicer combines the encoded divided segments of contentback together into an encoded content stream 2246. Because the content2240 is divided, each encoder can operate at rates that are less thanthe rate at which the unencoded content 2240 is being received. As aresult, the encoders 2230-2232 can provide accurate encoding at reducedrates and/or enhanced encoding while still accelerating encoding rates,in some implementations approaching and/or achieving real time rates. Insome embodiments, the splicer 2236 is implemented in the host computer,in alternative embodiments, however, the splicer can be implementedthrough independent hardware, one or more separate computers, processorsand/or combinations thereof. The encoded segments are stitched backtogether using, for example, compressed stream concatenation techniquessuch that the concatenated and encoded stream 2246 is compliant withdesired buffer models and/or encoding standards (e.g., AVC, VC1, andother such standards) with relatively minimal and preferably no qualityloss.

In dividing or temporally splitting the stream, the dicer generatessegments to be encoded that are complete or closed such that eachsegment does not reference and is not referenced by other picturesoutside the segment. As indicated above, the dicer dividing or splitpoints can be determined by available buffer levels, complete pictureboundaries (e.g., taking into account film frame to video frameconversion), entry point alignment and/or other relevant factors. Theprediction algorithm for “in” and “out” buffer levels can be furtherutilized to identify potential target slicing points for the segments inattempts to meet buffer models. The spliced encoded stream is typicallyfurther evaluated to determine whether the buffer models are achieved,and re-encoding is utilized as described above to satisfy desiredmodels.

In some implementations, the base or initial encoded data 2246 is storedin a first file. One or more additional files can be maintained forstoring re-encoded segments. The one or more files or additional filescan be utilized to record bit count adjustments, segment qualitysmoothing, chapter point insertions and/or other encoding adjustments. Amapping or links are recorded and maintained that identify thoseportions of the initial encoded data that were re-encoded, where chapterpoints were inserted and other manipulations generated. Additionally,those buffer models for which the encoded content does not comply and/orcannot be met can additionally be recorded. Upon completion of thesegment based re-encodes and other adjustments, the final encodedcontent is written, for example as described above with reference toprocess 520 of FIG. 5, where the models that are not satisfied aredesignated (e.g., designated in a header), and the re-encoded segmentsare retrieved from the one or more additional files to replace theinitial encoded segments identified to be re-encoded.

The encoder system 2220 attempts to encode at predefined rates, forexample at real time because the production work flow of uncompressedcontent data (e.g., high definition video) may be received from asource, such as a tape machine, and is being transferred across a datalink to the encoder system as a whole in real time, where the system maynot be able to stop the data flow and thus accepts the content at thatfeed rate. Some alternative embodiments stage the data, such as throughadditional buffers and operate at lower rates. This staging, however,can be impractical for some content given the size of typical data.Other embodiments attempt to encode at real time rates. The system 2220can be assembled, in some embodiments, through off the shelf componentsusing standard networks and/or busses, thus attempting to avoidobsolescence and/or leverage faster processors and components as theybecome available.

FIG. 23 depicts a simplified block diagram representation of a stream ofcontent 2240 that is divided by the dicer 2222 into divided segments2242. The content 2240, when comprising video content, is typicallyreceived as a string of pictures or frames 2320, where each frametypically comprises data defining a plurality of pixels. The unencodedcontent is supplied to the dicer 2222.

FIG. 24 depicts a simplified block diagram of an example implementationof a dicer 2222 according to some embodiments, where the dicer 2222 isimplemented at least in part through a hardware architecture. The dicerincludes a content stream receiver 2422, dicing processor unit 2424,memory 2426, audio extractor 2430, output ports 2432, and controller2434. The content stream receiver 2422 can be implemented in someembodiments at least in part through a serial digital interface (SDI)receiver (e.g., SMPTE292M) that receives the streaming, unencodedcontent 2240. The dicing processor unit 2424 can include a fieldprogrammable gate array for dicing the content (e.g., video) andcommunicating with a host (e.g., over a PCI bus), a microprocessorand/or other processor or combination of processors. The memorytypically includes one or more buffer memories, preferably deep orrelatively large commodity memory(s) that absorb the segments, and arelarge enough to handle practical segment sizes according to expectedencoding schemes, such as sizes of about 50 frames or more (e.g.,approximately 250 MB or more for each encoding processor unit), however,other sizes can be employed depending on the expected data to bereceived and/or encoding scheme to be employed.

The ports 2432 can be substantially any port, and in someimplementations include multiple firewire ports (e.g., 1394b-800 Mbpsfirewire ports) that deliver the divided segments to the encoderprocessor units 2230-2232 (see FIG. 22). In some embodiments, thecontent stream includes visual and audio content. As such the audioextractor 2430 extracts audio from the receiver and delivers it to thehost and/or alternate processor for processing. The controller 2434provides overall control of the dicer 2222 including machine controlservices.

FIG. 25 depicts a simplified block diagram of an example a host system2238 of the encoding system 2220 of FIG. 22. The host system 2238 caninclude a central controller 2522, a transcoder 2524, content router2526, and graphical user interface (GUI) controller 2530. In someembodiments, the dicer 2222 and/or the splicer 2236 are part of the host2238. The central controller 2522 manages the encoding system 2220coordinating at least the dicing and splicing. In some embodiments thecentral controller 2522 is implemented through one or moremicroprocessors and/or computers that employs an operating system 2532and accesses and runs software, such as a library of software forcontrolling the acquisition of content from sources such as cameras,video tape recorder (VTR) decks and other sources. The operating systemcan be, for example, Microsoft Windows XP, Linux or other operatingsystems that provide an overall layer of control and cooperates the hostwith other systems and/or programs, such as other content source and/orediting systems (e.g., Microsoft's DirectShow™, QuickTime™ and othersuch systems). The controller 2522 can further monitor encoding and/orinclude additional monitors that monitor the compliance of the bufferlevels of the encoder processor units 2230. The router 2526 in partcontrols delivery of the content stream 2240 to the dicer 2222. In someimplementations, the router delivers the content as file based content.The GUI 2530 provides an interface through which a user can manipulate,control and alter the system operations, provide parameters, thresholdsand/or other information, and/or obtain reports, statistics, resultsand/or view encoded content (including entire stream and/or re-encodedsegments).

Referring back to FIGS. 22 and 23, in operation the encoding system 2220receives the content, divides the content into divided segments throughthe dicer 2222, encodes the divided segments, and splices the encodeddivided segments back together as an encoded output stream 2246. Thedicer 2222 receives the uncompressed input 2240 that is to be dividedinto a series of divided segments 2331-2336, with each segmentcontaining a plurality of frames 2320. The divided segments aretypically defined by grouping a set of frames in succession. The dicerseparates the divided segments and delivers the segments to differentbuffers 2224-2226. For example, a first divided segment 2331 isdelivered to a first encoder buffer 2224, where the segment comprises aplurality of frames S1+0 through S1+n. A second divided segment 2332 isdelivered to the second buffer 2225, and the third divided segment 2333is delivered to the third buffer 2226. If the system only includes threeencoders, a fourth segment 2334 is typically delivered to the firstbuffer 2224, the fifth segment 2335 to the second buffer 2225 and so on.It is noted, however, that in some implementations the segments are notequal in length and/or content and thus upon recycling to the firstbuffer 2224, the first buffer may still contain content beyond athreshold due to one or more prior segments being sufficiently large,and the dicer skips the first buffer and evaluates subsequent buffersfor delivering the divided segments. Further, the system can includesubstantially any number of encoding processing units.

The divided segments 2331-2336 can include substantially any number ofpictures or frames, and each divided segment does not necessarilyinclude the same number of frames. Some embodiments utilize I-frames asdivided segment boundaries, thus these divided segments start with anI-frame.

One of the benefits provided by the encoding system 2220 is that theencoding processor units 2230-2232 are connected to a buffer 2224-2226and draw content data from the buffer at a rate that is less than therate at which the data 2240 is being received (e.g., real time rate).Therefore, the encoding processor units 2230-2232 can operate at ratesthat are less than received data rates. For example, if the data iscoming in at a real time full rate, and there are three encoderprocessor units 2230-2232, each encoding processor unit can effectivelyoperate at about one third the rate of the received content, with thesum of the three encoding processor units providing effectively anencoding rate about equal to the received rate. By paralleling theencoding processing, the encoding system 2220 increases the operatingbandwidth. In some embodiments, the encoding processor units 2230-2232are operated at rates so that the summation of the parallel encodingexceeds the rate of the received input signal 2240 to in part compensatefor delays introduced by the processing. For example with three encodingprocessor units, each encoding processor unit can be implemented tooperate at about 35-40% the data rates of the input content 2240,effectively provide 105-120% encoding rates, where the addition +5-20%compensates for the overhead processing time associated with dicing,buffering, splicing and/or other potential processing overhead.

FIG. 26 depicts a block diagram of a portion of the encoding system 2220further detailing at least the dicer 2222, encoding control, andfeedback according to some embodiments. The system includes an imagecomplexity analyzer 2622, a control loop 2624, an optional errorfeedback processor 2626, a control loop compensator 2630, mappingfunction 2632, target buffer level distributor 2634, delay buffer 2640,dicer distributor 2642, and an optional temporal correlation analyzer2644.

The image complexity analyzer 2622 performs an analysis of thecomplexity of the content stream 2240, such as video data. Based on thecomplexity determination, the complexity analyzer generates complexityparameters and/or guides that relate to buffer levels that may be usedat given points relative to the content stream. Generally, the morecomplex the data, the more buffer levels the system tends to be usingsuch that typically the more complex the content stream the more bufferspace needed. This relationship between complexity to buffer level needsis typically not a linear relationship.

FIG. 27 depicts a simplified graphical representation of a complexityprofile or mapping 2720 of a content stream scaled to unity that mightbe generated through the complexity analyzer 2622. Referring to FIGS. 26and 27, the complexity analyzer 2622 generates complexity parameters orscales that are utilized to adjust encoding levels of the encodingprocessor units 2230-2232 in attempts to satisfy desired decoder bufferlevel models. Generally, as the complexity increases the encoding ratesare increased.

In some embodiments, the complexity analyzer 2622 is implemented atleast in part through an MPEG2 encoder and/or other simplified encoderto predict the complexity. For example, the complexity analyzer can atleast in part be implemented through an off the self MPEG2 encoder thatis set to operate in a fixed quant or quality mode. The fixed qualitymode operates and encodes generally without regard to a buffer level anddata bit rates. Instead the encoder performs a free-form encoding. Theencoded content of the picture or frame processed through the fixedquant encoder results in an encoded picture having an arbitrary datasize. The data size can be used in some embodiments as a reflection ofthe complexity of encoding of that frame. Still other embodiments mayemploy an AVC, VC1 or other encoder as part of the complexity analyzerwhen processing capabilities are available. Other complexity analysescan also be employed such as intra frame analysis comparing standarddeviations from a mean pixel value with dynamic range used, inter frameanalysis comparing intra measures from picture to picture, comparison ofhistograms from picture to picture, motion analysis measuring thecorrelation in motion vectors, and/or other analyses.

The system then defines a complexity parameter (which in someembodiments is the data size of the encoded frame) and stores thecomplexity parameter. Based on a series of complexity parameters of thecontent stream 2224, a complexity mapping 2720 of the data set (e.g.,content stream) is defined, and in some implementations has agranularity of a picture or granularity of a GOP. In some instances, thecomplexity mapping is summed to get an entire mapping for a dividedsegment that is being processed through the system.

Some implementations of the encoding system include the optional errorfeedback processor 2626 that receives error feedback 2660 based on theresulting encoded content. The error feedback processor processes theerrors into error parameters 2662. In some instances, the feedback isreceived from the encoding processor units that return informationrelative to the difficulty the encoding processor units had in meetingdefined encoding target levels indicating an accuracy of the complexityanalyzer and/or mapping function.

These difficulty parameters can then be utilized by the control loop2630 to adjust the mapping function as described fully below. Thecontrol loop provides buffer level predictions to the encoding processorunits that is adapted through the feedback based on error responses fromthe encoding processor units. Additionally and/or alternatively, thecontrol loop 2630 can adjust the mapping function based on thedetermined complexity of a current frame or divided segment and how thatcomplexity data relates to previous complexity data for previous framesor divided segments (e.g., by evaluating quantization levels).

The control loop 2630 compares the complexity profile and/or thefeedback parameters in attempts to determine whether the encoderprocessor units are encoding at desired rates. Differences or deltasbetween what the system specifies as encoding rates and the rates atwhich the encoder processor units are performing can affect the systemoperation and are perpetuated at least to the buffer levels. Forexample, when the encoder processor units perform at rates less thanspecified, data is not pulled from the buffers at rates equal to therates at which data is supplied and the buffer levels increase more thanexpected which can affect the levels of encoding of subsequent frames.Similarly, if the encoder processor units operate at rates aboveexpectation, the buffer level will be lower.

Based on the control loop comparison, the control loop compensator 2630defines compensation parameters. The compensation parameters are used inthe mapping function 2632 to modify a mapping to improve the complexityprediction as the data is processed. This allows for the adjustment ofthe mapping function during processing and/or in real time, as themapping function is effectively an approximation that is contentdependent. Alternative embodiments employ a two pass process byinitiating a complexity analysis of the entire stream. Following theanalysis, the complexity is then utilized to control the encodingprocessor units. Those systems employing the two pass process typicallydo not include the look ahead buffer 2640 as the complexity parametersare already known based upon the pass to adjust encoding processorunits.

The mapping function 2632, in some embodiments, employs a second orthird order polynomial as the mapping function. The mapping is suppliedto the target buffer level distributor 2634 that generates buffer leveltarget rates 2670 that are supplied to the encoding processor units2230-2232 to adjust and/or maintain the encoding rates in attempts tosatisfy desired or expected buffer levels. A table or spreadsheet can beutilized in some embodiments to implement the adjustments in the mappingfunction. For example, one or more look up tables can be utilized thatcontain desired encoding buffer levels for different levels of datarates. Additionally and/or alternatively, the tables can define sets ofpolynomials that can be employed depending on the identified complexity,data rates and/or error feedback as analyzed by the control loopcompensator 2630.

The adjustments to the mapping function can be implemented continuouslyto allow continuous adjustments to encoding rates. In otherimplementations, the adjustments to encoding rates and/or desired bufferlevels are implemented at divided segment boundaries (where boundariesare typically the last frame of one divided segment and/or the beginningof a subsequent divided segment). This adjustment of encoding ratesattempts to achieve a desired target buffer level for the add point fora particular segment that covers the start point for following dividedsegments. The encoding processor units utilize the buffer level targetrates 2670 in attempts to meet that goal, while the system continues toreceive the feedback 2660 with respect to the difficulty in meeting thegoals.

As described above, the dicer 2222 divides the content stream 2240 intoa plurality of divided segments 2331-2336. The determination of theboundaries between the divided segments can be based on predefinedperiodic number of frames, predefined amounts of time, the complexity ofthe content 2240, and other parameters or combinations of parameters.For example, in some simplified implementations of the presentembodiments, the divided segment boundaries can be set blindly based ona period of time (e.g., every one second of time) without regard to thecontent. The encoding processor units then encode divided segments toalign with that one second of time boundary allowing the resultingencoded divided segments to be pieced together at the end. Selecting thedivided segment boundaries without regard to the content (e.g.,periodically based on time or number of frames) can often result in lessthan optimal coding quality.

Some embodiments alternatively utilize the complexity analysis 2720 toidentify positions within the content stream 2240 where boundaries canbe implemented between divided segments 2331-2336 that provide moreaccurate encoding and/or distribute the encoding processing more evenlyover the plurality of encoding processor units. In utilizing thecomplexity analysis the system attempts to align the dividing segmentboundaries to an appropriate point within the content. For example withvideo content, a boundary point can be selected at a point within thecontent that include high action and/or has less correlation (lessreferencing between frames) over time (e.g., scene change or a fastshot). In many instances it is desirable to position I-frames atportions of the content that have high action or has less correlation,and this allows many of the divided segments 2331-2336 to have anI-frame at the beginning of each grouped segment.

Still referring to FIGS. 26 and 27, the system can employ the delay orlook ahead buffer 2640, at least in part, to allow time to identifypotential divided segment boundaries. This delay buffer can provide adelay, for example of 1 second, however, substantially any delay can beutilized depending on the system and available system resources. Thisallows the image complexity data 2720 to be received by the dicerdistributor 2642 prior to receiving the content stream to be diced andencoded. By looking ahead on the complexity data, the dicer distributor2642 has time to evaluate the complexity and identify positions wheredivided segment boundaries can be defined that correlate with highaction, less correlation and/or other locations along the stream whereboundaries can be selected.

Some embodiments further include a temporal correlation analyzer 2644that aids in identifying divided segment boundaries. The temporalcorrelation analyzer 2644 can detect large spikes in data rates from onepicture to the next that can indicate scene changes and/or high action,thus the complexity typically increases. Additionally and/oralternatively, some embodiments utilize the MPEG2 encoder of the imagecomplexity analyzer 2622 to identify transitions in GOP structuresoutputted from the MPEG2 encoder that indicate positions along thecontent stream where the MPEG2 encoder detected scene changes.Typically, MPEG2 encoders include relatively good scene detection, andsuch scene detection can be used to identify divide segment boundaries.

Further, the temporal correlation analyzer 2644, in someimplementations, further identifies frame boundaries that also maintaintelecine boundaries. The temporal correlation analyzer can include atelecine detection algorithm that identifies a change in frame rates,for example changes from content originally recorded for video (e.g.,television content containing about 30 frames per second for U.S.television) verses content originally recorded for motion picture film(e.g., content containing 24 frames per second). As is known in the art,the conversion of motion picture film content to television contentemploys the repeating of fields. As such, some implementations of thetemporal correlation analyzer attempt to define divided segmentboundaries while maintaining the telecine boundaries (e.g., avoidingdividing fields). In some instances, the temporal correlation analyzerutilizes a separate MPEG encoder, or utilizes the MPEG encoder of theimage complexity analyzer as some MPEG encoders detect telecineboundaries.

Referring to FIGS. 22, 23 and 26, based on the determined dividedsegment boundaries the dicer 2642 divides up on the content into thedivided segments 2331-2336. These divided segments are then forwarded tothe encoder processing units 2230-2232 for encoding. Once the groupedsegments are encoded, the encoded content is forwarded to the splicer2236 that combines the encoded divided segments into a single stream2246.

The encoding processor units 2230-2232 can be operated, in someembodiments, on one of a plurality of different operational modes. Forexample, one mode of operation sets the encoding processor units to meetdefined encoding schemes regardless of the resulting quality. Analternative mode of operation defines a limit or threshold quality levelbelow which the encoding processor unit ignores the encoding schemeparameters and maintains a signal quality level and thus may fail tosatisfy one or more decoder buffer models. The system then employs thesegment based re-encode to go back and address those areas of theencoded content that fail to meet signal quality levels and/or fail tomeet decoder models where the re-encoding can include adjusting theencoding rate to improve quality, transrating in attempts to meet bufferlevel parameters and/or other encoding techniques or combinations oftechniques.

Some embodiments provide in part for segment based re-encoding thatimproves the resulting encoded content, allows the encoded content tomeet one or more desired encoding standards without having to perform acomplete re-encode of the entire content, and producing overall betterquality as the encoding rates can be varied over the content stream.Additionally, some embodiments provide for the ability to incorporatecustom GOP placement within the content after a base encode has alreadybeen completed without having to resort to fully re-encoding the entirestream. Further, the custom GOP placement can be implemented byre-encoding a small portion of the encoded content.

Allowing for the custom GOP placement provides a user with greaterflexibility and control over the resulting encoded product, and cansignificantly reduce processing time and overhead. For example, a usermay initiate a base encode and following that encode realize that itwould be beneficial to include an additional chapter point, or a usermay have forgotten to include chapter points. Some present embodimentsallow for the insertion of chapter points and other content organizationafter the base encode without the hassle and time expense in re-encodingthe entire content stream. Further, the present embodiments allow forthe insertion of chapter points or other content organization, and/orprovides for custom GOP placement through segment based re-encodes,while still maintaining the level of the encoded content such that theencoded content satisfies desired decoder buffer models.

In encoding content, such as in digital video disc (DVD) creation, usersoften want to define and/or position GOPs in specific places so they canput, for example, a chapter point at that point or location. In someprior systems, the user had to specify the locations of chapter pointsprior to a base encode so that the encoder could incorporate the GOPs atthe specified locations. Failing to define the desired GOP structuresand/or chapter points in prior systems before the base encode typicallyrequired the user to go back, define the GOPs and/or chapter points andimplement a completely new full encode of the entire content steam.

Some present embodiments, however, allow a user to employ the segmentbased re-encode to define GOP structures, chapter points, otherorganization input, and/or otherwise alter the encoded content whilestill satisfying decoder standards after an initial base encode and/orsubsequent encodes. Thus, some embodiments provide mechanisms for goingback after a base encode and/or subsequent encodes to incorporate newGOPs without having to re-encode the entire data set. Following anencode or with content previously encoded, a user can identify positionsalong the encoded stream where chapter points, GOP structures and/orother content organization is to be positioned and the system canimplement the segment based re-encode to insert the desired GOP, chapterpoint and/or other organization. Therefore, some embodiments allow forthe creation of GOPs, the insertion of chapter points and/or otherorganization, after the encoding has taken place. In some instances, thealtering of the GOP structure and/or the insertion of a chapter pointincludes the conversion or promotion of a B- or P-frame to an I-frame,effectively truncating or extending the GOP structure and creating a newGOP starting from about a desired location.

FIG. 28 depicts a simplified flow diagram of a process 2820 according tosome embodiments for the insertion of a chapter point and/or thealtering of GOP structures. In step 2822 the location of chapterinsertion or the point where the GOP structure is to be altered isidentified. In some instances, the chapter insertion point is defined bya user. In step 2824, the process identifies a candidate re-encode startpoint picture or frame that is distanced from the defined insertionpoint. Typically, to incorporate the desired chapter point and redefinethe GOP structure, the re-encode start point picture is selected adistance from the desired location so that the segment re-encode canadjust the referencing between pictures so that the chapter insertionpoint is not hindered by picture references. Often the system defines anew GOP structure at the insertion point and thus redefines the picturetypes such that an I-picture exists at the desired insertion point.

In step 2826 the candidate start point picture is evaluated. Typically,this evaluation is similar to the evaluation preformed in process 820 ofFIG. 8. In step 2830 it is determined whether the candidate start pointpicture is a valid start point picture. When the candidate start pointis valid, the process continues to step 2836. Alternatively when thecandidate start point is not valid, step 2832 is entered where analternate candidate start point is identified and the process returns tostep 2826 for evaluation.

When a valid start point picture is identified, the process proceeds tostep 2836 where a candidate end point picture is identified. Againtypically, the candidate end point is selected a distance from thedefined insertion point such that the identified start point picture andthe candidate end point picture straddle the defined insertion point. Instep 2840 the candidate end point picture is evaluated. This evaluation,in some embodiments is similar to the evaluation performed in theprocess 820 of FIG. 8. In step 2842 it is determined whether thecandidate end point picture is a valid end point picture. When thecandidate end point is not valid, step 2844 is entered where analternate candidate end point is identified and the process returns tostep 2840. Alternatively, when the endpoint is valid, step 2850 isentered where the segment re-encode is initiated to re-encode thesegment defined between the identified start and end points. In step2852 the desired GOP restructuring and/or chapter point is insertedduring the segment re-encode at about the desired location, for exampleby altering the picture type at about the defined insertion point. Insome embodiments, the process 2820 can identify a plurality of potentialstart and end points and allow the user to select which of the pluralityof start and end points are to be used. The process repeats for eachchapter point insertion and/or GOP adjustment.

Further, some embodiments allow for content to be encoded in order tomeet defined bit budget parameters, such as limiting content to bestored onto a portable storage medium, while still meeting desireddecoder buffer models. In meeting a bit budget, some embodiments canstart an initial or base encode, where the encoding can be based onsubstantially any relevant encoding scheme and can include fixed orvariable bit rate encoding, in attempts to satisfy one or more decoderbuffer models. Following the initial encode, subsequent segmentre-encodes may be initiated as described above to address errors and/orfailures to meet one or more desired decoder models. Additionally and/oralternatively, the total bit count can be determined for the encodedcontent. The total bit count can be compared with a desired or maximumbit count or budget. If the total bit count exceeds the bit budget theencoded content can be evaluated to identify one or more areas orsegments where the content can be re-encoded at lower levels to reducethe bits utilized for the one or more segments such that the total bitcount meets the desired bit budget while still maintaining the qualityof the encoded content to meet desired decoder buffer models.

In some embodiments, the initial encoding can be implemented such thatthe bit count of the initially encoded content is limited to about afirst fixed amount. For example, a video stream to be encoded and storedon a portable optical storage medium with limited storage capacity, suchas 5 Gbytes, can be encoded through an initial encoding such that theencoded content has a total bit count that is less than the maximum(e.g., 5 Gbytes) by a predefined amount (e.g., 10 to 20%) to provide amargin of error and head room.

Following the initial encoding and through the use of segmentre-encoding, some embodiments can then increase the bit rates of one ormore specific segments, thus improving quality, and using some or all ofthe available overhead (e.g., the addition 1 Gbyte). Further, someembodiments additionally allow for segment based re-encoding of somesegments to decrease bit rates of some segments to allow for theincreasing of rates in other segments. Still further, if more than theoverhead storage area is needed to achieve encoded content that meet thedesired decoder buffer models and/or standards, the present embodimentscan evaluate the content to identify areas that have some headroom withrespect to buffer models or standards and implement re-encodes of thoseareas to reduce the overall total bit count and/or to free up bits fromthose areas that exceed the acceptable bit rates, and using the freed upcapacity to re-encode sections that fail to satisfy one or more buffermodels. Therefore, this system improves the overall quality of the videocompared to previous methods.

Some embodiments additionally allow for a variable bit rate over thelength of the content stream. Many prior encoding systems use constantbit rates. For these constant bit rate encoders to encode content thatdid not exceed defined bit count limits, the systems calculated anamount of time or memory space available, determine a bit rate thatwould be within the bit count limit, and encode the entire contentstream with that constant bit rate. The constant bit rate encoding oftenresults in some portions of the content having much different qualitythan other portions.

Additionally, some embodiments can utilize the segment based re-encodingin attempts to moderate encoded content such that the signal qualityresulting from the decode has less variation. In many instances, aviewer of video content more readily notices areas of lower quality whenthe content has relatively significant or large changes in quality thancontent that has a slightly lower overall quality yet has smaller orless quality variations. Some embodiments can apply a variable bit rateby reducing the quality of sections of the encoded content that arerelatively high in quality (e.g., by comparing PSNR values) and applythe freed up capacity to the sections of encoded content that are lowerin quality in attempts to try and even out the quality levels along thecontent stream and/or limit large changes in signal quality withinpredefined amounts of the content, while achieving an overall increasein quality.

Some embodiments also provide for the reallocation of bits over a streamof content through transcoding. The encoded content can be evaluatedbased for example on signal quality (e.g., PSNR) to identify portions ofthe stream where transcoding provides for the freeing up of bits withoutadversely or minimally affecting the quality. The portions of the streamto be transcoded can also be identified through other methods such asidentifying portions where the motion vectors are diverse, areas withcoarse quantization, macroblock effects, areas with redundancy, andother similar methods.

Additionally and/or alternatively, some embodiments in someimplementations free up bits by converting I-frames to P-frames orB-frames. This conversion may be limited for certain applications,protocols and/or standards, for example, because of defined I-frame toB- and/or P-frame ratios. Still further reductions in bit count can beachieved in some embodiments through pre-filtering of the content. Insome implementations, the content is filtered using one or morefiltering techniques, such as but not limited to, median filtering,spatial filtering, temporal filtering, noise filtering, and/or otherrelevant filtering or combinations of filtering. The filtering canadditionally and/or alternatively be applied during segment basedre-encoding allowing a user to avoid applying a filter to an entirestream and instead applying the filtering to the selected segment orsegments (e.g., portions of the content having fast action or rapidscene changes). Additionally, the filtering can be implemented during are-encode at higher or harder levels to induce additional filtering ofat least some segments to reduce bit count. In some instances, thefiltering and/or the level of filtering applied is adjustable and/orselectable by a user to achieve desired results.

In identifying segments on which to apply filtering and/or re-encoding,the quality of the content can be evaluated, for example, based onmotion vector(s), quantifiers and/or combinations thereof. Wellorganized or ordered vectors tend to indicate good encoding while randomand/or poorly ordered motion vectors tend to indicate inaccurateencoding. Typically, however, some embodiments do not rely on the motionvectors exclusively as some content, such as video content that includesrain, weather, clouds, zooming in, and the like, can be difficult toencode and may not be detected as effectively using motion vectorsand/or quantifier values.

FIG. 29 depicts a simplified flow diagram of a process 2920 for use inadjusting the total bit count to meet or be below a desired bit budget.In step 2922, a content stream is encoded through an initial or baseencode such that the resulting encoded stream satisfy a predefined bitbudget (e.g., 4 Gbits). In step 2924, the encoded stream is evaluated todetermine whether a segment of the encoded stream fails one or moredecoder models. As indicated above, the evaluation of the encoded streamcan be initiated on the stream while being encoded and prior to a fullencode.

In step 2926, the bit rates for the segments identified as in violationof one or more buffer models are decreased and are re-encoded such thatthey satisfy the desired buffer model(s). In step 2930, a total bitcount is identified and the process 2920 determines whether the totalcount exceeds a defined maximum bit count. In those instances where thetotal bit count does not exceed the maximum bit count the process 2920terminates.

When it is determined in step 2930 that the total bit exceeds a maximum,the process skips to step 2934 where a segment that has a quality thatexceed buffer model thresholds by a largest margin is identified. Insome instances the segments within a predefined distance or number offrames are reviewed and the segment with the largest margin within thatdistance or number of frames is selected. In step 2936, the identifiedsegment with the maximum quality margin is re-encode at lower bit rateto free up additional bits. The process 2920 then returns to step 2930to determine whether the total bit count is less than the desiredmaximum count. In some alternative configurations of the process 2920,the re-encode of the failed segment is not performed until a sufficientamount of capacity is freed up for the failed segment to be re-encoded.

FIG. 30 depicts a simplified flow diagram of a process 3020 for use insmooth or limiting quality changes over a content stream. In step 3022,one or more segments having a lowest quality level or a quality levelthat is below a first threshold limit are identified. In step 3024, theprocess determines whether one or more segments are identified that havehigh quality levels and/or have quality levels that exceed the qualitylevels of the one or more segments with the lowest quality by a secondthreshold and are within predefined ranges or numbers of frames of theone or ore segments identified in step 3022. The predefined range candepend on many factors, such as buffer fill levels, buffer levelshifting, predefined number of GOPs, rate of data transfer and/or othersuch factors. In step 3026 one or more of the identified segments withthe high quality levels are re-encode at lower bit rate. In step 3030the one or more segments identified with the low quality are re-encodedat increased rates.

In step 3032, the process determines whether a total bit count exceedsmaximum total bit count. If the total bit count exceeds the maximum,step 3034 is entered where it is determined whether there is anadditional segment having a high quality or a quality that exceeds thequality of another segment within predefined ranges or numbers of framesof the lower quality segment. When there is a segment with a highquality level the segment is re-encoded at lower a bit rate in step3036, and the process returns to step 3032. If there is not a segmentthat has a relatively high quality level, step 3040 is entered where there-encoded content with a quality that is below the first threshold isdeleted and not utilized, and the process terminates.

When it is determined in step 3032 that the total bit count does notexceed a maximum, the process enters step 3042 where it determineswhether the total bit count is within a limit of the maximum bit count.If the total count is not within the limit, the process returns to step3022 to further identify additional segments to re-encode to even outand/or improve encoded quality, otherwise the process terminates.

The re-encoding and/or adjusting of the quality of content toredistribute bit budgeting can be implemented through some embodimentswithout user interaction. In some embodiments, however, prior toinitiating a shift of bits to reduce the quality of high qualitysegments to allow for increasing the quality of low quality segments,some embodiments generate a time line for a user that identifies ormarks those areas where it may be beneficial to adjust the quality. Thesystem then allows the user to select adjustments if any and toimplement the adjustments when desired. Additionally and/oralternatively, the system can be configured to generate the time linethat identifies and labels the quality of segments and/or frames basedon a predefined quality measure or scale (which in some instances can beselected by the user). Based on the labeled quality, the system can beconfigured to allow for a manual operation where the user can evaluatethe stream of content and define areas of re-encode and/or qualityadjustment.

As introduced above, some embodiments can be implemented throughhardware, software, firmware and/or combinations thereof. Further, someembodiments can encode uncompressed high definition content, such asvisual video content at accelerated rates (e.g., at about the rate thecontent is received) from a source, such as from sources over serialdigital cables (e.g., SMPTE292M). The encoding can be performed in someimplementations at real time rates, and can provide for transcoding ofthe high definition content in file form (e.g., AVI, Quicktime, Rawframes, and the like). Some systems are configured to be adaptable tochanges in standards and new encoding formats, while allowing foradjustments and/or fixes in quality and feature enhancements. Someembodiments are implemented utilizing commodity components and areeasily adaptable to take advantage of processor speed advancements andcapabilities.

While the invention herein disclosed has been described by means ofspecific embodiments and applications thereof, numerous modificationsand variations could be made thereto by those skilled in the art withoutdeparting from the scope of the invention set forth in the claims.

1. A method for use in encoding content, the method comprising:receiving source content; encoding the source content producing encodedcontent; evaluating a first encoded segment of the encoded contentrelative to a plurality of buffer models; determining whether the firstsegment of encoded content is to be re-encoded relative to one or moreof the plurality of buffer models based on the evaluating; andre-encoding the first segment when it is determined that the firstsegment is to be re-encoded.
 2. The method of claim 1, wherein thedetermining whether the first segment of the encoded content is to bere-encoded comprises determining whether the encoded content fails afirst buffer model of the plurality of buffer models; and there-encoding comprises re-encoding the first segment when it isdetermined that the encoded content fails a first buffer model.
 3. Themethod of claim 2, further comprising: identifying that the encodedcontent fails a second buffer model of the plurality of buffer models;invalidating the second buffer model relative to the encoded content. 4.The method of claim 3, wherein the invalidating the second buffer modelcomprises replacing parameters of the second buffer model withparameters from a fourth buffer model that is a valid buffer model. 5.The method of claim 1, further comprising: identifying a second segmentof the encoded content; re-encoding the second segment freeing up bits;and the re-encoding of the first segment comprises re-encoding the firstsegment to utilize the freed up bits.
 6. The method of claim 1, furthercomprising: identifying a third segment; identifying that a chapterpoint is to be inserted into the encoded content relative to the thirdsegment; re-encoding the third segment incorporating a chapter point. 7.The method of claim 1, wherein the re-encoding the first segmentcomprises re-encoding the first segment creating a first re-encodedsegment; storing the first re-encoded segment separate from the encodedcontent; and finalizing the encoding of the source content comprisingmerging the first re-encoded content with the encoded content andadjusting a buffer level and access unit information of the encodedcontent with buffer level and access unit information of the firstre-encoded segment.
 8. The method of claim 1, wherein the evaluating ofthe first encoded segment comprises substantially simultaneouslydecoding a portion of the first encoded segment according to a pluralityof distinct buffer models.
 9. The method of claim 1, wherein theencoding the content comprises: identifying segments of the sourcecontent; separating the segments of the source content; separatelyencoding the segments of the source content producing encoded dividedsegments; splicing the encoded divided segments producing an encodedcontent stream.
 10. The method of claim 9, further comprising:identifying a complexity of the source content; adjusting buffer levelsaccording to the identified complexity for the segments of the sourcecontent.
 11. The method of claim 9, further comprising: evaluatingtemporal correlations of the source content; identifying boundarieswithin the source content such that the identifying of the segments ofthe source content comprises defining the segments according to theidentified boundaries.
 12. A method for use in encoding multimediacontent, the method comprising: initiating an encoding of a sourcecontent producing encoded content; identifying a segment of the encodedcontent to be re-encoded; identifying a first candidate start point fora re-encoding of the segment; determining whether the first candidatestart point is a valid start point by evaluating a first portion of theencoded content relative to the first candidate start point; and settingthe first candidate start point as a valid re-encode start point whenthe first candidate start point is validated.
 13. The method of claim12, wherein the determining whether the first candidate start point isvalid comprises determining whether the first portion of the contentprior to the first candidate start point is referenced by a secondportion of the content following the first candidate start pointrelative to a playback timeline; and implementing the setting of thefirst candidate start point as the re-encode start point when the secondportion of the content following the first candidate start point doesnot reference the first portion of the content prior to the firstcandidate start point.
 14. The method of claim 12, further comprising:identifying a first candidate end point for the re-encoding of thesegment; determining whether the first candidate end point is a validend point by evaluating a fourth portion of the encoded content relativeto the first candidate end point; and setting the first candidate endpoint as a valid re-encode end point when the first candidate end pointis validated.
 15. The method of claim 14, wherein determining whetherthe first candidate end point is valid comprises determining whether atleast a portion of content within a candidate segment between the validre-encode start point and the first candidate end point is referenced bycontent outside the candidate segment; and implementing the setting ofthe first candidate end point as the valid re-encode end point when theat least the portion of the content within the candidate segment is notreferenced by content outside the candidate segment.
 16. The method ofclaim 12, wherein the determining whether the first candidate startpoint is valid comprises accessing an index for a frame prior to thefirst candidate start point relative to a playback timeline anddetermining whether the index contains a listing of a frame followingthe first candidate start point relative to the playback timeline; andimplementing the setting of the first candidate start point as there-encode start point when the index does not contains the listing ofthe frame following the first candidate start point.
 17. The method ofclaim 12, further comprising: upgrading the first candidate start pointto an intraframe.
 18. A method for use in encoding multimedia content,the method comprising: initiating an encoding of a source contentproducing encoded content; identifying a segment of the encoded contentto be re-encoded; identifying a first candidate end point for there-encoding of the segment; determining whether the first candidate endpoint is a valid end point by evaluating a fourth portion of the encodedcontent relative to the first candidate end point; and setting the firstcandidate end point as a valid re encode end point when the firstcandidate end point is validated.
 19. A method for use in encodingcontent, comprising: receiving source content; encoding the sourcecontent producing encoded content; identifying a total bit count for theencoded content; determining whether the total bit count has apredefined relationship with a threshold bit count; and re-encoding oneor more segments of the encoded content producing one or more re-encodedsegments such that an adjusted total bit count with the re-encodedsegments has the predefined relationship with the threshold bit countwhen the total bit count does not have the predefined relationship withthe threshold bit count.
 20. The method of claim 19, wherein there-encoding one or more segments comprises: identifying a first segmentof the encoded content that has a quality level that has a predefinedrelationship with a buffer model threshold; re-encoding the firstsegment producing a first re-encoded segment such that the firstre-encoded segment utilizes an amount of bits that is less than anamount of bits utilized by the first segment.
 21. The method of claim20, further comprising: evaluating a second encoded segment of theencoded content relative to a plurality of buffer models; determiningwhether the second segment of encoded content is to be re-encodedrelative to one or more of the plurality of buffer models based on theevaluating; and re-encoding the second segment when it is determinedthat the second segment is to be re-encoded.
 22. The method of claim 20,further comprising: identifying one or more additional segments of theencoded content that have quality levels that have predefinedrelationships with the buffer model threshold; re-encoding the one ormore additional segments producing additional re encoded segments suchthat the adjusted bit count has a margin that exceeds the predefinedrelationship relative to the threshold bit count; and implementing there-encoding of the second segment when the adjusted bit count has themargin that exceeds the predefined relationship relative to thethreshold bit count.
 23. A method for use in encoding multimediacontent, comprising: identifying one or more first segments of encodedcontent having a quality level having a predefined relationship with afirst threshold limit; determining whether one or more additionalsegments having quality levels that have a predefined relationship witha second threshold level and are within predefined ranges from one ormore of the first segments; re-encoding one or more of the additionalsegments producing one or more re-encoded additional segments havingquality levels such that the re-encoded additional segments utilizefewer bits than the one or more additional segments; and re-encoding oneor more of the first segments producing one or more re-encoded firstsegments such that the one or more re-encoded first segments havequality levels that are greater than the quality levels of thecorresponding first segment.
 24. The method of claim 23, furthercomprising: determine whether a total bit count exceeds a maximum totalbit count; determined whether there is one or more further additionalsegments having a quality level that has a predefined relationship witha third threshold level and are within the predefined ranges of the oneor more first segments; and re-encoding one or more of the furtheradditional segments producing one or more further additional re-encodedsegments such that the one or more further additional re-encodedadditional segments utilize fewer bits than the one or more furtheradditional segments.
 25. A method for use in formatting content,comprising: parsing an encoded multimedia content stream identifyingparameters of the content stream; altering one of the identifiedparameters; simulating at least a partial decoding of the encodedcontent stream based on the altered parameter; identifying whether abuffer threshold is exceed; and modifying the encoded content streamaccording to the altered parameter when the buffer threshold is notexceeded.
 26. The method of claim 25, wherein the modifying furthercomprises rewriting a field of the encoded content stream based on thealtered parameter.
 27. The method of claim 25, wherein the identifyingwhether the buffer threshold is exceeded comprises determining whetheran overflow threshold and an underflow threshold are exceeded.
 28. Themethod of claim 25, further comprising: determining whether parametersof the encoded content stream match parameters of the encoded contentstream with the altered parameter; and halting the simulating of the atleast the partial decoding when parameters of the encoded content streammatch parameters of the encoded content stream with the alteredparameter.
 29. The method of claim 25, further comprising: identifyingparameter boundaries such that the buffer threshold is not exceeded. 30.The method of claim 29, wherein the identifying of the parameterboundaries comprises identifying a maximum bit rate that does not causean underflow and an overflow.
 31. The method of claim 29, wherein theidentifying of the parameter boundaries comprises implementing thesimulating of the at least the partial decoding based on a model havingsubstantially an infinite buffer size.
 32. The method of claim 29,further comprising: shifting an amount of buffer availability based onone or more of the identified parameter boundaries.
 33. The method ofclaim 29, further comprising: re-encoding a first segment of the encodedcontent stream producing a re-encoded content stream; identifying aparameter of the re-encoded segment; and merging the parameter of there-encoded segment with the identified parameters of the encoded contentstream.
 34. The method of claim 33, further comprising: re-encoding asecond segment of the encoded content based at least in part on themerged parameter of the re-encoded segment and the identified parametersof the encoded content stream.
 35. The method of claim 33, furthercomprising: identifying that the encoded content stream fails a buffermodel; replacing the identified parameter with a parameter for analternate buffer model.
 36. A method for use facilitating an encoding ofdigital content, comprising: generating a bit rate track graphicallyrepresenting bit rates for portions of encoded content; generating aquality track graphically representing a quality of encoding of theportions of encoded content that corresponds with the bit rate track;and identifying in the bit rate track a selection of a portion of theencoded content to be re-encoded.
 37. The method of claim 36, furthercomprising: generating an entry point track graphically representingentry points, where the entry point track corresponds with the bit ratetrack; and generating a picture structure track graphically representingpicture structures of the encoded content, where the picture structuretrack corresponds with the bit rate track.
 38. The method of claim 36,further comprising: providing selectable re-encode start point and endpoint options; and providing zooming capabilities to zoom in and out onat least the bit rate track.
 39. The method of claim 36, furthercomprising: generating a bit rate indication for a selected segment ofcontent; registering an input moving the bit rate indicator.
 40. Themethod of claim 39, wherein the bit rate indicator is a bit rate barthat is selectable and moveable by a user.
 41. The method of claim 39,further comprising: a bit rate value corresponding with a positioning ofthe bit rate indication.
 42. The method of claim 36, further comprising:generating settings options comprising a quality threshold and a segmentlength parameter; identifying segments within the encoded content thathave quality levels that are below the quality threshold and meet thesegment length parameter.
 43. The method of claim 36, furthercomprising: generating a list of selected segments and defining a statusof each segment in the list.